Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2013/oss vna

2013-11-30T18:40:46Z

Vshesha: /* Known Issues */

== Introduction ==
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities to manage peer reviews in coursework. Expertiza is built on Ruby on Rails platform. It uses the mysql db as the backend datatbase. More information on Expertiza can be found [https://github.com/expertiza/expertiza here]. Experitza is an open source project. The source code can be forked from [https://github.com/expertiza/expertiza github] and cloned for making modifications.

Our main focus in this OSS project was on the Class: controllers/assignment_controller.rb. This controller handles interaction with an instructor who is creating or editing an assignment. Various issues in the assignments controller and the suitable code changes have been explained in the following sections.

== Project Requirements ==
1. Topics tab is non-functional, but should do what the popup menu item “Add/edit signup sheet” does. 
2. Rubrics tab should show “Teammate Review:” option if “Has Teams?” is selected and “Maximum number of members per team” is greater than 0 in General Tab. 
3. The code should retrieve timezonepref of current user in Due dates tab. Also, time/date picker asks a user to specify the hours, minutes, and seconds of a due date. 
:3.1 Use a time/date picker that doesn’t show seconds. 
:3.2 Minutes should be in the step size 5. 
:3.3 Seconds field should not be displayed 
4. Refactoring 
5. Tests for all the functionality mentioned above

== Implementation ==
This section gives brief details of all the implementations done for project E801.
=== Topics Tab ===
The requirement of this implementation was to make topics tab functional. This tab is mainly responsible to display a page where user can create a topic for a assignment and can see already created topics for that assignment.

====Initial Design====
Ideally, when we click on topics tab, it should display what the popup menu item “Add/edit signup sheet” does.
1.Go to Manage->Assignments
2.For a assignment, click on edit signup sheet
However, in main expertiza project, topics tab was non-functional as shown below. To check Topics tab, follow below mentioned steps: 
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Go to “Topics” tab (You will not be able to view existing topics and create new ones)

[[File:Topics-before.png]]
====Design Considerations====
The Topics tab should ideally render "sign_up_sheet\add_signup_topcis.html.erb" partial, but to reuse this partial, Assignments would need to have several other attributes like 'sign_up_topics', 'slots_filled', 'slots_waitlisted', which are not really properties of an assignment. Hence, a new partial for adding topics "assignments/edit/add_signup_topics.html.erb" has been added. Partials for 'table_header', 'table_line', 'add_topics' from "sign_up_sheet" have been modified to be accessed from other views as well and re-used.
Also, the option to add new topics should be available only if 'Has Topics' has been checked.

====Modified Design====
In our implemented project, Topics tab shows already existing topics for an assignment and link to create a new topic where a user can create a new topic. This is similar to popup menu item “Add/edit signup sheet”.
One can follow the same steps as mentioned above to view the functionality:
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Go to “Topics” tab (You should be able to view existing topics and create new ones)
 

[[File:topics-after.png]]

=== Teammate Review Rubric===
====Initial Design====
While editing or creating an assignment the Teammate Review rubric shows up irrespective of whether the assignment is a team assignment or not. It should ideally only show up if the assignment under consideration has teams.
====Modified Design====
Now, the Teammate Review rubric shows up under the Rubrics tab, only if “Has Teams?” is selected and “Maximum number of members per team” is greater than 0 in General Tab.
 
One can follow the below mentioned steps to view the functionality:
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Click on “General” tab
4.Check “Has teams?” and give “Maximum number of members per team” greater than 0.
5.Save assignment
6.Go to “Rubrics” tab. Check if “Teammate Review:” is present.
7.Repeat the same process with “Has Teams?” unchecked and “Maximum number of members” equal to 0. This will not display “Teammate Review:” in the Rubrics tab.

[[File:teams.png]]

[[File:rubric.png]]

=== Refactoring===
Requirements for this section were centered around the following points:
 1. Renaming set_up method. It does not indicate its functionality.
 2. Refactoring copy method
 3. Fixing spell check issue for "Maximum number of review per team"

====Initial Design====
1. set_up method is badly named. It does not indicate what functionality it implements. This method is present in assignments controller. 
2. "Maximum number of review" under rubrics tab is not spelled correctly. This can be found under :
Manage->Assignments->Edit Assignment->Rubrics
3. "copy" method in assignments controller is too long.

====Modified Design====
1. set_up has been renamed to set_up_assignment_review to better reflect what it actually implements. 
2. "Maximum number of review" has been renamed to "Maximum number of reviews". 
3. "copy" method has been refactored by moving some of its functionality into its respective method copy_assignment_questionnaire. 

=== Timezone Issue ===
====Initial Design====
Time zones are not handled properly in the code. The code should retrieve the Preferred Time Zone of the current user and pre-select it in the time/date picker. Also, the time/date picker asks a user to specify the hours, minutes, and seconds of a due date. Obviously we don’t care about seconds, so it would be nice to use a time/date picker that doesn’t show seconds and minutes are in steps of 5. Also daylight savings time needs to be taken care of.

[[File:Time_zone_before.png]]

====Modified Design====
The above mentioned issues are addressed and can be viewed by following the below mentioned steps:
1.Go to Profile. Set timezone to any new timezone and save it.
2.Go to Manage-> Assignments
3.Click on “Edit Assignment” image for any of the assignments
4.Go to “Due dates” tab. Click on the textfield for “Round 1: Submission”. You can find that it doesn’t show seconds and minutes are in the step size 5, also, in “Time Zone”, it shows the timezone set in the earlier step.

[[File:profile.png]]
[[File:Time_zone.png]]

==Code changes==
Following is the code change in the app/views/assignments/edit._due_dates.html.erb file :

jQuery('#datetimepicker_' + element_id).datetimepicker({
dateFormat: 'yy/mm/dd',
timeFormat: 'HH:mm z',
controlType: 'select',
timezoneList: [{value:'<%=Time.zone_offset(@user.timezonepref)%>', label: '<%=@user.timezonepref.split("\s")[0]%>'}]

The Zone_offset picks the time zone set by user in the profile tab and sets it as default

==Known Issues==
Certain timezones like Arizona are obsolete. However these are listed under available timezones as they are rendered by the form helper. When such timezones are used, the time is saved properly, but it is known to cause issues while changing timezones. In order to avoid such issues, use standard timezones. Ex: Mountain Time Zone instead of Arizona etc.

==Testing==

Capybara DSL was selected for running the tests in this project. Testing was concentrated around assignment controller and profile tab as the project modified code around these areas.

===Configuration===
1) First, add Capybara to your Gemfile:
group :development, :test do
gem 'rspec-rails'
gem 'capybara'
end
Run bundle install

2) In spec/spec_helper.rb, add two require calls for Capybara near the top:
ENV["RAILS_ENV"] ||= 'test'
require File.expand_path("../../config/environment", __FILE__)
require 'rspec/rails'

# Add this to load Capybara integration:
require 'capybara/rspec'
require 'capybara/rails'

3) In spec/spec_helper.rb, add
config.include Capybara::DSL

===Test database===
Prepare the test db as follows
$ rake db:prepare:test
$ rake db:migrate RAILS_ENV=test
$ rake db:test:load
$ rake db:seed RAILS_ENV=test
$ rake db:migrate RAILS_ENV=test

===Tests===
Following are the 3 main tests that were written to check the modified code.

Test1 : profile_spec.rb
Assertion : Ensure user can set default timezone

Test2 : due_date_spec.rb
Assertion : User should be able to change due dates

Test3 : topic_spec.rb
Assertion : User should be able to create sign up topics by clicking the topic tab in edit assignment page

In addition to the above tests, the following tests were added to check the sanity of the code
Creating an assignment
Login as admin
Open home page

The tests were run in ruby 1.9.3 environment sucessfully.

==Future work ==
In order to further refactor the assignments_controller.rb
 
:1. No usages for the following methods were found:
::- copy_participants_from_course
::- define_instructor_notification_limit

:2. Following methods can be moved to Model classes but are non-functional(throwing errors) in the existing code itself.
::-associate_assignment_with_course
::-remove_assignment_from_course

:3. Methods that add to and delete from delayed_queue should be in the delayed_queue class.(Part of different project)

:4. Due date formatting can be improvised.

== External Links ==
# [https://github.com/expertiza/expertiza Expertiza]
# [https://github.com/vshesha/expertiza/ E801_Expertiza]
# [http://152.46.18.166:3000/ Demo]
# [http://jqueryui.com/datepicker/ Datepicker]
# [http://trentrichardson.com/examples/timepicker/ Timepicker]
# [http://guides.rubyonrails.org/layouts_and_rendering.html Layouts and Rendering in Rails]

CSC/ECE 517 Fall 2013/oss vna

2013-11-30T18:39:34Z

Vshesha: /* Timezone Issue */

== Introduction ==
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities to manage peer reviews in coursework. Expertiza is built on Ruby on Rails platform. It uses the mysql db as the backend datatbase. More information on Expertiza can be found [https://github.com/expertiza/expertiza here]. Experitza is an open source project. The source code can be forked from [https://github.com/expertiza/expertiza github] and cloned for making modifications.

Our main focus in this OSS project was on the Class: controllers/assignment_controller.rb. This controller handles interaction with an instructor who is creating or editing an assignment. Various issues in the assignments controller and the suitable code changes have been explained in the following sections.

== Project Requirements ==
1. Topics tab is non-functional, but should do what the popup menu item “Add/edit signup sheet” does. 
2. Rubrics tab should show “Teammate Review:” option if “Has Teams?” is selected and “Maximum number of members per team” is greater than 0 in General Tab. 
3. The code should retrieve timezonepref of current user in Due dates tab. Also, time/date picker asks a user to specify the hours, minutes, and seconds of a due date. 
:3.1 Use a time/date picker that doesn’t show seconds. 
:3.2 Minutes should be in the step size 5. 
:3.3 Seconds field should not be displayed 
4. Refactoring 
5. Tests for all the functionality mentioned above

== Implementation ==
This section gives brief details of all the implementations done for project E801.
=== Topics Tab ===
The requirement of this implementation was to make topics tab functional. This tab is mainly responsible to display a page where user can create a topic for a assignment and can see already created topics for that assignment.

====Initial Design====
Ideally, when we click on topics tab, it should display what the popup menu item “Add/edit signup sheet” does.
1.Go to Manage->Assignments
2.For a assignment, click on edit signup sheet
However, in main expertiza project, topics tab was non-functional as shown below. To check Topics tab, follow below mentioned steps: 
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Go to “Topics” tab (You will not be able to view existing topics and create new ones)

[[File:Topics-before.png]]
====Design Considerations====
The Topics tab should ideally render "sign_up_sheet\add_signup_topcis.html.erb" partial, but to reuse this partial, Assignments would need to have several other attributes like 'sign_up_topics', 'slots_filled', 'slots_waitlisted', which are not really properties of an assignment. Hence, a new partial for adding topics "assignments/edit/add_signup_topics.html.erb" has been added. Partials for 'table_header', 'table_line', 'add_topics' from "sign_up_sheet" have been modified to be accessed from other views as well and re-used.
Also, the option to add new topics should be available only if 'Has Topics' has been checked.

====Modified Design====
In our implemented project, Topics tab shows already existing topics for an assignment and link to create a new topic where a user can create a new topic. This is similar to popup menu item “Add/edit signup sheet”.
One can follow the same steps as mentioned above to view the functionality:
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Go to “Topics” tab (You should be able to view existing topics and create new ones)
 

===Code Changes==

[[File:topics-after.png]]

=== Teammate Review Rubric===
====Initial Design====
While editing or creating an assignment the Teammate Review rubric shows up irrespective of whether the assignment is a team assignment or not. It should ideally only show up if the assignment under consideration has teams.
====Modified Design====
Now, the Teammate Review rubric shows up under the Rubrics tab, only if “Has Teams?” is selected and “Maximum number of members per team” is greater than 0 in General Tab.
 
One can follow the below mentioned steps to view the functionality:
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Click on “General” tab
4.Check “Has teams?” and give “Maximum number of members per team” greater than 0.
5.Save assignment
6.Go to “Rubrics” tab. Check if “Teammate Review:” is present.
7.Repeat the same process with “Has Teams?” unchecked and “Maximum number of members” equal to 0. This will not display “Teammate Review:” in the Rubrics tab.

[[File:teams.png]]

[[File:rubric.png]]

=== Refactoring===
Requirements for this section were centered around the following points:
 1. Renaming set_up method. It does not indicate its functionality.
 2. Refactoring copy method
 3. Fixing spell check issue for "Maximum number of review per team"

====Initial Design====
1. set_up method is badly named. It does not indicate what functionality it implements. This method is present in assignments controller. 
2. "Maximum number of review" under rubrics tab is not spelled correctly. This can be found under :
Manage->Assignments->Edit Assignment->Rubrics
3. "copy" method in assignments controller is too long.

====Modified Design====
1. set_up has been renamed to set_up_assignment_review to better reflect what it actually implements. 
2. "Maximum number of review" has been renamed to "Maximum number of reviews". 
3. "copy" method has been refactored by moving some of its functionality into its respective method copy_assignment_questionnaire. 

=== Timezone Issue ===
====Initial Design====
Time zones are not handled properly in the code. The code should retrieve the Preferred Time Zone of the current user and pre-select it in the time/date picker. Also, the time/date picker asks a user to specify the hours, minutes, and seconds of a due date. Obviously we don’t care about seconds, so it would be nice to use a time/date picker that doesn’t show seconds and minutes are in steps of 5. Also daylight savings time needs to be taken care of.

[[File:Time_zone_before.png]]

====Modified Design====
The above mentioned issues are addressed and can be viewed by following the below mentioned steps:
1.Go to Profile. Set timezone to any new timezone and save it.
2.Go to Manage-> Assignments
3.Click on “Edit Assignment” image for any of the assignments
4.Go to “Due dates” tab. Click on the textfield for “Round 1: Submission”. You can find that it doesn’t show seconds and minutes are in the step size 5, also, in “Time Zone”, it shows the timezone set in the earlier step.

[[File:profile.png]]
[[File:Time_zone.png]]

==Code changes==
Following is the code change in the app/views/assignments/edit._due_dates.html.erb file :

jQuery('#datetimepicker_' + element_id).datetimepicker({
dateFormat: 'yy/mm/dd',
timeFormat: 'HH:mm z',
controlType: 'select',
timezoneList: [{value:'<%=Time.zone_offset(@user.timezonepref)%>', label: '<%=@user.timezonepref.split("\s")[0]%>'}]

The Zone_offset picks the time zone set by user in the profile tab and sets it as default

==Known Issues==
Certain timezones like Arizona are obsolete. However these are listed usder available timezones as they are rendered by the form helper. When such timezones are used it is known to cause issues while changing timezones. In order to avoid such issues, use standard timezones. Ex: Mountain Time Zone instead of Arizona etc.

==Testing==

Capybara DSL was selected for running the tests in this project. Testing was concentrated around assignment controller and profile tab as the project modified code around these areas.

===Configuration===
1) First, add Capybara to your Gemfile:
group :development, :test do
gem 'rspec-rails'
gem 'capybara'
end
Run bundle install

2) In spec/spec_helper.rb, add two require calls for Capybara near the top:
ENV["RAILS_ENV"] ||= 'test'
require File.expand_path("../../config/environment", __FILE__)
require 'rspec/rails'

# Add this to load Capybara integration:
require 'capybara/rspec'
require 'capybara/rails'

3) In spec/spec_helper.rb, add
config.include Capybara::DSL

===Test database===
Prepare the test db as follows
$ rake db:prepare:test
$ rake db:migrate RAILS_ENV=test
$ rake db:test:load
$ rake db:seed RAILS_ENV=test
$ rake db:migrate RAILS_ENV=test

===Tests===
Following are the 3 main tests that were written to check the modified code.

Test1 : profile_spec.rb
Assertion : Ensure user can set default timezone

Test2 : due_date_spec.rb
Assertion : User should be able to change due dates

Test3 : topic_spec.rb
Assertion : User should be able to create sign up topics by clicking the topic tab in edit assignment page

In addition to the above tests, the following tests were added to check the sanity of the code
Creating an assignment
Login as admin
Open home page

The tests were run in ruby 1.9.3 environment sucessfully.

==Future work ==
In order to further refactor the assignments_controller.rb
 
:1. No usages for the following methods were found:
::- copy_participants_from_course
::- define_instructor_notification_limit

:2. Following methods can be moved to Model classes but are non-functional(throwing errors) in the existing code itself.
::-associate_assignment_with_course
::-remove_assignment_from_course

:3. Methods that add to and delete from delayed_queue should be in the delayed_queue class.(Part of different project)

:4. Due date formatting can be improvised.

== External Links ==
# [https://github.com/expertiza/expertiza Expertiza]
# [https://github.com/vshesha/expertiza/ E801_Expertiza]
# [http://152.46.18.166:3000/ Demo]
# [http://jqueryui.com/datepicker/ Datepicker]
# [http://trentrichardson.com/examples/timepicker/ Timepicker]
# [http://guides.rubyonrails.org/layouts_and_rendering.html Layouts and Rendering in Rails]

CSC/ECE 517 Fall 2013/oss vna

2013-11-07T01:31:08Z

Vshesha: /* Testing */

== Introduction ==
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities to manage peer reviews in coursework. Expertiza is built on Ruby on Rails platform. It uses the mysql db as the backend datatbase. More information on Expertiza can be found [https://github.com/expertiza/expertiza here]. Experitza is an open source project. The source code can be forked from [https://github.com/expertiza/expertiza github] and cloned for making modifications.

Our main focus in this OSS project was on the Class: controllers/assignment_controller.rb. This controller handles interaction with an instructor who is creating or editing an assignment. Various issues in the assignments controller and the suitable code changes have been explained in the following sections.

== Project Requirements ==
1. Topics tab is non-functional, but should do what the popup menu item “Add/edit signup sheet” does. 
2. Rubrics tab should show “Teammate Review:” option if “Has Teams?” is selected and “Maximum number of members per team” is greater than 0 in General Tab. 
3. The code should retrieve timezonepref of current user in Due dates tab. Also, time/date picker asks a user to specify the hours, minutes, and seconds of a due date. 
:3.1 Use a time/date picker that doesn’t show seconds. 
:3.2 Minutes should be in the step size 5. 
:3.3 Seconds field should not be displayed 
4. Refactoring 
5. Tests for all the functionality mentioned above

== Implementation ==
This section gives brief details of all the implementations done for project E801.
=== Topics Tab ===
The requirement of this implementation was to make topics tab functional. This tab is mainly responsible to display a page where user can create a topic for a assignment and can see already created topics for that assignment.

====Initial Design====
Ideally, when we click on topics tab, it should display what the popup menu item “Add/edit signup sheet” does.
1.Go to Manage->Assignments
2.For a assignment, click on edit signup sheet
However, in main expertiza project, topics tab was non-functional as shown below. To check Topics tab, follow below mentioned steps: 
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Go to “Topics” tab (You will not be able to view existing topics and create new ones)

[[File:Topics-before.png]]

====Modified Design====
In our implemented project, Topics tab shows already existing topics for an assignment and link to create a new topic where a user can create a new topic. This is similar to popup menu item “Add/edit signup sheet”.
One can follow the same steps as mentioned above to view the functionality:
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Go to “Topics” tab (You should be able to view existing topics and create new ones)
 
[[File:topics-after.png]]

=== Teammate Review Rubric===
====Initial Design====
While editing or creating an assignment the Teammate Review rubric shows up irrespective of whether the assignment is a team assignment or not. It should ideally only show up if the assignment under consideration has teams.
====Modified Design====
Now, the Teammate Review rubric shows up under the Rubrics tab, only if “Has Teams?” is selected and “Maximum number of members per team” is greater than 0 in General Tab.
 
One can follow the below mentioned steps to view the functionality:
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Click on “General” tab
4.Check “Has teams?” and give “Maximum number of members per team” greater than 0.
5.Save assignment
6.Go to “Rubrics” tab. Check if “Teammate Review:” is present.
7.Repeat the same process with “Has Teams?” unchecked and “Maximum number of members” equal to 0. This will not display “Teammate Review:” in the Rubrics tab.

[[File:teams.png]]

[[File:rubric.png]]

=== Refactoring===
Requirements for this section were centered around the following points:
 1. Renaming set_up method. It does not indicate its functionality.
 2. Refactoring copy method
 3. Fixing spell check issue for "Maximum number of review per team"

====Initial Design====
1. set_up method is badly named. It does not indicate what functionality it implements. This method is present in assignments controller. 
2. "Maximum number of review" under rubrics tab is not spelled correctly. This can be found under :
Manage->Assignments->Edit Assignment->Rubrics
3. "copy" method in assignments controller is too long.

====Modified Design====
1. set_up has been renamed to set_up_assignment_review to better reflect what it actually implements. 
2. "Maximum number of review" has been renamed to "Maximum number of reviews". 
3. "copy" method has been refactored by moving some of its functionality into its respective method copy_assignment_questionnaire. 

=== Timezone Issue ===
====Initial Design====
Time zones are not handled properly in the code. The code should retrieve the Preferred Time Zone of the current user and pre-select it in the time/date picker. Also, the time/date picker asks a user to specify the hours, minutes, and seconds of a due date. Obviously we don’t care about seconds, so it would be nice to use a time/date picker that doesn’t show seconds and minutes are in steps of 5. Also daylight savings time needs to be taken care of.

[[File:Time_zone_before.png]]

====Modified Design====
The above mentioned issues are addressed and can be viewed by following the below mentioned steps:
1.Go to Profile. Set timezone to any new timezone and save it.
2.Go to Manage-> Assignments
3.Click on “Edit Assignment” image for any of the assignments
4.Go to “Due dates” tab. Click on the textfield for “Round 1: Submission”. You can find that it doesn’t show seconds and minutes are in the step size 5, also, in “Time Zone”, it shows the timezone set in the earlier step.

[[File:profile.png]]
[[File:Time_zone.png]]

==Testing==

Capybara DSL was selected for running the tests in this project. Testing was concentrated around assignment controller and profile tab as the project modified code around these areas.

===Configuration===
1) First, add Capybara to your Gemfile:
group :development, :test do
gem 'rspec-rails'
gem 'capybara'
end
Run bundle install

2) In spec/spec_helper.rb, add two require calls for Capybara near the top:
ENV["RAILS_ENV"] ||= 'test'
require File.expand_path("../../config/environment", __FILE__)
require 'rspec/rails'

# Add this to load Capybara integration:
require 'capybara/rspec'
require 'capybara/rails'

3) In spec/spec_helper.rb, add
config.include Capybara::DSL

===Test database===
Prepare the test db as follows
$ rake db:prepare:test
$ rake db:migrate RAILS_ENV=test
$ rake db:test:load
$ rake db:seed RAILS_ENV=test
$ rake db:migrate RAILS_ENV=test

===Tests===
Following are the 3 main tests that were written to check the modified code.

Test1 : profile_spec.rb
Assertion : Ensure user can set default timezone

Test2 : due_date_spec.rb
Assertion : User should be able to change due dates

Test3 : topic_spec.rb
Assertion : User should be able to create sign up topics by clicking the topic tab in edit assignment page

In addition to the above tests, the following tests were added to check the sanity of the code
Creating an assignment
Login as admin
Open home page

The tests were run in ruby 1.9.3 environment sucessfully.

==Future work ==
In order to further refactor the assignments_controller.rb
 
:1. No usages for the following methods were found:
::- copy_participants_from_course
::- define_instructor_notification_limit

:2. Following methods can be moved to Model classes but are non-functional(throwing errors) in the existing code itself.
::-associate_assignment_with_course
::-remove_assignment_from_course

:3. Methods that add to and delete from delayed_queue should be in the delayed_queue class.(Part of different project)

:4. Due date formatting can be improvised.

== External Links ==
# [https://github.com/expertiza/expertiza Expertiza]
# [https://github.com/vshesha/expertiza/ E801_Expertiza]
# [http://152.46.18.166:3000/ Demo]
# [http://jqueryui.com/datepicker/ Datepicker]
# [http://trentrichardson.com/examples/timepicker/ Timepicker]
# [http://guides.rubyonrails.org/layouts_and_rendering.html Layouts and Rendering in Rails]

CSC/ECE 517 Fall 2013/oss vna

2013-10-30T05:38:50Z

Vshesha: /* Future work */

== Introduction ==
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities to manage peer reviews in coursework. Expertiza is built on Ruby on Rails platform. It uses the mysql db as the backend datatbase. More information on Expertiza can be found [https://github.com/expertiza/expertiza here]. Experitza is an open source project. The source code can be forked from [https://github.com/expertiza/expertiza github] and cloned for making modifications.

Our main focus in this OSS project was on the Class: controllers/assignment_controller.rb. This controller handles interaction with an instructor who is creating or editing an assignment. Various issues in the assignments controller and the suitable code changes have been explained in the following sections.

== Project Requirements ==
1. Topics tab is non-functional, but should do what the popup menu item “Add/edit signup sheet” does. 
2. Rubrics tab should show “Teammate Review:” option if “Has Teams?” is selected and “Maximum number of members per team” is greater than 0 in General Tab. 
3. The code should retrieve timezonepref of current user in Due dates tab. Also, time/date picker asks a user to specify the hours, minutes, and seconds of a due date. 
:3.1 Use a time/date picker that doesn’t show seconds. 
:3.2 Minutes should be in the step size 5. 
:3.3 Seconds field should not be displayed 
4. Refactoring 
5. Tests for all the functionality mentioned above

== Implementation ==
This section gives brief details of all the implementations done for project E801.
=== Topics Tab ===
The requirement of this implementation was to make topics tab functional. This tab is mainly responsible to display a page where user can create a topic for a assignment and can see already created topics for that assignment.

====Initial Design====
Ideally, when we click on topics tab, it should display what the popup menu item “Add/edit signup sheet” does.
1.Go to Manage->Assignments
2.For a assignment, click on edit signup sheet
However, in main expertiza project, topics tab was non-functional as shown below. To check Topics tab, follow below mentioned steps: 
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Go to “Topics” tab (You will not be able to view existing topics and create new ones)

[[File:Topics-before.png]]

====Modified Design====
In our implemented project, Topics tab shows already existing topics for an assignment and link to create a new topic where a user can create a new topic. This is similar to popup menu item “Add/edit signup sheet”.
One can follow the same steps as mentioned above to view the functionality:
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Go to “Topics” tab (You should be able to view existing topics and create new ones)
 
[[File:topics-after.png]]

=== Teammate Review Rubric===
====Initial Design====
While editing or creating an assignment the Teammate Review rubric shows up irrespective of whether the assignment is a team assignment or not. It should ideally only show up if the assignment under consideration has teams.
====Modified Design====
Now, the Teammate Review rubric shows up under the Rubrics tab, only if “Has Teams?” is selected and “Maximum number of members per team” is greater than 0 in General Tab.
 
One can follow the below mentioned steps to view the functionality:
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Click on “General” tab
4.Check “Has teams?” and give “Maximum number of members per team” greater than 0.
5.Save assignment
6.Go to “Rubrics” tab. Check if “Teammate Review:” is present.
7.Repeat the same process with “Has Teams?” unchecked and “Maximum number of members” equal to 0. This will not display “Teammate Review:” in the Rubrics tab.

[[File:teams.png]]

[[File:rubric.png]]

=== Refactoring===
Requirements for this section were centered around the following points:
 1. Renaming set_up method. It does not indicate its functionality.
 2. Refactoring copy method
 3. Fixing spell check issue for "Maximum number of review per team"

====Initial Design====
1. set_up method is badly named. It does not indicate what functionality it implements. This method is present in assignments controller. 
2. "Maximum number of review" under rubrics tab is not spelled correctly. This can be found under :
Manage->Assignments->Edit Assignment->Rubrics
3. "copy" method in assignments controller is too long.

====Modified Design====
1. set_up has been renamed to set_up_assignment_review to better reflect what it actually implements. 
2. "Maximum number of review" has been renamed to "Maximum number of reviews". 
3. "copy" method has been refactored by moving some of its functionality into its respective method copy_assignment_questionnaire. 

=== Timezone Issue ===
====Initial Design====
Time zones are not handled properly in the code. The code should retrieve the Preferred Time Zone of the current user and pre-select it in the time/date picker. Also, the time/date picker asks a user to specify the hours, minutes, and seconds of a due date. Obviously we don’t care about seconds, so it would be nice to use a time/date picker that doesn’t show seconds and minutes are in steps of 5. Also daylight savings time needs to be taken care of.

[[File:Time_zone_before.png]]

====Modified Design====
The above mentioned issues are addressed and can be viewed by following the below mentioned steps:
1.Go to Profile. Set timezone to any new timezone and save it.
2.Go to Manage-> Assignments
3.Click on “Edit Assignment” image for any of the assignments
4.Go to “Due dates” tab. Click on the textfield for “Round 1: Submission”. You can find that it doesn’t show seconds and minutes are in the step size 5, also, in “Time Zone”, it shows the timezone set in the earlier step.

[[File:profile.png]]
[[File:Time_zone.png]]

==Testing==

Capybara DSL was selected for running the tests in this project.

===Configuration===
1) First, add Capybara to your Gemfile:
group :development, :test do
gem 'rspec-rails'
gem 'capybara'
end
Run bundle install

2) In spec/spec_helper.rb, add two require calls for Capybara near the top:
ENV["RAILS_ENV"] ||= 'test'
require File.expand_path("../../config/environment", __FILE__)
require 'rspec/rails'

# Add this to load Capybara integration:
require 'capybara/rspec'
require 'capybara/rails'

3) In spec/spec_helper.rb, add
config.include Capybara::DSL

===Test database===
Prepare the test db as follows
$ rake db:prepare:test
$ rake db:migrate RAILS_ENV=test
$ rake db:test:load
$ rake db:seed RAILS_ENV=test
$ rake db:migrate RAILS_ENV=test

===Tests===
Following are the 3 main tests that were written to check the modified code.

Test1 : profile_spec.rb
Assertion : Ensure user can set default timezone

Test2 : due_date_spec.rb
Assertion : User should be able to change due dates

Test3 : topic_spec.rb
Assertion : User should be able to create sign up topics by clicking the topic tab in edit assignment page

In addition to the above tests, the following tests were added to check the sanity of the code
Creating an assignment
Login as admin
Open home page

The tests were run in ruby 1.9.3 environment sucessfully.

==Future work ==
In order to further refactor the assignments_controller.rb
 
:1. No usages for the following methods were found:
::- copy_participants_from_course
::- define_instructor_notification_limit

:2. Following methods can be moved to Model classes but are non-functional(throwing errors) in the existing code itself.
::-associate_assignment_with_course
::-remove_assignment_from_course

:3. Methods that add to and delete from delayed_queue should be in the delayed_queue class.(Part of different project)

:4. Due date formatting can be improvised.

== External Links ==
# [https://github.com/expertiza/expertiza Expertiza]
# [https://github.com/vshesha/expertiza/ E801_Expertiza]
# [http://152.46.18.166:3000/ Demo]
# [http://jqueryui.com/datepicker/ Datepicker]
# [http://trentrichardson.com/examples/timepicker/ Timepicker]
# [http://guides.rubyonrails.org/layouts_and_rendering.html Layouts and Rendering in Rails]

CSC/ECE 517 Fall 2013/oss vna

2013-10-30T05:37:18Z

Vshesha: /* Tests */

== Introduction ==
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities to manage peer reviews in coursework. Expertiza is built on Ruby on Rails platform. It uses the mysql db as the backend datatbase. More information on Expertiza can be found [https://github.com/expertiza/expertiza here]. Experitza is an open source project. The source code can be forked from [https://github.com/expertiza/expertiza github] and cloned for making modifications.

Our main focus in this OSS project was on the Class: controllers/assignment_controller.rb. This controller handles interaction with an instructor who is creating or editing an assignment. Various issues in the assignments controller and the suitable code changes have been explained in the following sections.

== Project Requirements ==
1. Topics tab is non-functional, but should do what the popup menu item “Add/edit signup sheet” does. 
2. Rubrics tab should show “Teammate Review:” option if “Has Teams?” is selected and “Maximum number of members per team” is greater than 0 in General Tab. 
3. The code should retrieve timezonepref of current user in Due dates tab. Also, time/date picker asks a user to specify the hours, minutes, and seconds of a due date. 
:3.1 Use a time/date picker that doesn’t show seconds. 
:3.2 Minutes should be in the step size 5. 
:3.3 Seconds field should not be displayed 
4. Refactoring 
5. Tests for all the functionality mentioned above

== Implementation ==
This section gives brief details of all the implementations done for project E801.
=== Topics Tab ===
The requirement of this implementation was to make topics tab functional. This tab is mainly responsible to display a page where user can create a topic for a assignment and can see already created topics for that assignment.

====Initial Design====
Ideally, when we click on topics tab, it should display what the popup menu item “Add/edit signup sheet” does.
1.Go to Manage->Assignments
2.For a assignment, click on edit signup sheet
However, in main expertiza project, topics tab was non-functional as shown below. To check Topics tab, follow below mentioned steps: 
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Go to “Topics” tab (You will not be able to view existing topics and create new ones)

[[File:Topics-before.png]]

====Modified Design====
In our implemented project, Topics tab shows already existing topics for an assignment and link to create a new topic where a user can create a new topic. This is similar to popup menu item “Add/edit signup sheet”.
One can follow the same steps as mentioned above to view the functionality:
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Go to “Topics” tab (You should be able to view existing topics and create new ones)
 
[[File:topics-after.png]]

=== Teammate Review Rubric===
====Initial Design====
While editing or creating an assignment the Teammate Review rubric shows up irrespective of whether the assignment is a team assignment or not. It should ideally only show up if the assignment under consideration has teams.
====Modified Design====
Now, the Teammate Review rubric shows up under the Rubrics tab, only if “Has Teams?” is selected and “Maximum number of members per team” is greater than 0 in General Tab.
 
One can follow the below mentioned steps to view the functionality:
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Click on “General” tab
4.Check “Has teams?” and give “Maximum number of members per team” greater than 0.
5.Save assignment
6.Go to “Rubrics” tab. Check if “Teammate Review:” is present.
7.Repeat the same process with “Has Teams?” unchecked and “Maximum number of members” equal to 0. This will not display “Teammate Review:” in the Rubrics tab.

[[File:teams.png]]

[[File:rubric.png]]

=== Refactoring===
Requirements for this section were centered around the following points:
 1. Renaming set_up method. It does not indicate its functionality.
 2. Refactoring copy method
 3. Fixing spell check issue for "Maximum number of review per team"

====Initial Design====
1. set_up method is badly named. It does not indicate what functionality it implements. This method is present in assignments controller. 
2. "Maximum number of review" under rubrics tab is not spelled correctly. This can be found under :
Manage->Assignments->Edit Assignment->Rubrics
3. "copy" method in assignments controller is too long.

====Modified Design====
1. set_up has been renamed to set_up_assignment_review to better reflect what it actually implements. 
2. "Maximum number of review" has been renamed to "Maximum number of reviews". 
3. "copy" method has been refactored by moving some of its functionality into its respective method copy_assignment_questionnaire. 

=== Timezone Issue ===
====Initial Design====
Time zones are not handled properly in the code. The code should retrieve the Preferred Time Zone of the current user and pre-select it in the time/date picker. Also, the time/date picker asks a user to specify the hours, minutes, and seconds of a due date. Obviously we don’t care about seconds, so it would be nice to use a time/date picker that doesn’t show seconds and minutes are in steps of 5. Also daylight savings time needs to be taken care of.

[[File:Time_zone_before.png]]

====Modified Design====
The above mentioned issues are addressed and can be viewed by following the below mentioned steps:
1.Go to Profile. Set timezone to any new timezone and save it.
2.Go to Manage-> Assignments
3.Click on “Edit Assignment” image for any of the assignments
4.Go to “Due dates” tab. Click on the textfield for “Round 1: Submission”. You can find that it doesn’t show seconds and minutes are in the step size 5, also, in “Time Zone”, it shows the timezone set in the earlier step.

[[File:profile.png]]
[[File:Time_zone.png]]

==Testing==

Capybara DSL was selected for running the tests in this project.

===Configuration===
1) First, add Capybara to your Gemfile:
group :development, :test do
gem 'rspec-rails'
gem 'capybara'
end
Run bundle install

2) In spec/spec_helper.rb, add two require calls for Capybara near the top:
ENV["RAILS_ENV"] ||= 'test'
require File.expand_path("../../config/environment", __FILE__)
require 'rspec/rails'

# Add this to load Capybara integration:
require 'capybara/rspec'
require 'capybara/rails'

3) In spec/spec_helper.rb, add
config.include Capybara::DSL

===Test database===
Prepare the test db as follows
$ rake db:prepare:test
$ rake db:migrate RAILS_ENV=test
$ rake db:test:load
$ rake db:seed RAILS_ENV=test
$ rake db:migrate RAILS_ENV=test

===Tests===
Following are the 3 main tests that were written to check the modified code.

Test1 : profile_spec.rb
Assertion : Ensure user can set default timezone

Test2 : due_date_spec.rb
Assertion : User should be able to change due dates

Test3 : topic_spec.rb
Assertion : User should be able to create sign up topics by clicking the topic tab in edit assignment page

In addition to the above tests, the following tests were added to check the sanity of the code
Creating an assignment
Login as admin
Open home page

The tests were run in ruby 1.9.3 environment sucessfully.

==Future work ==
In order to further refactor the assignments_controller.rb
 
:1. No usages for the following methods were found:
::- copy_participants_from_course
::- define_instructor_notification_limit

:2. Following methods can be moved to Model classes but are non-functional(throwing errors) in the existing code itself.
::-associate_assignment_with_course
::-remove_assignment_from_course

:3. Methods that add to and delete from delayed_queue should be in the delayed_queue class.(Part of different project)

== External Links ==
# [https://github.com/expertiza/expertiza Expertiza]
# [https://github.com/vshesha/expertiza/ E801_Expertiza]
# [http://152.46.18.166:3000/ Demo]
# [http://jqueryui.com/datepicker/ Datepicker]
# [http://trentrichardson.com/examples/timepicker/ Timepicker]
# [http://guides.rubyonrails.org/layouts_and_rendering.html Layouts and Rendering in Rails]

CSC/ECE 517 Fall 2013/oss vna

2013-10-30T05:34:50Z

Vshesha: /* Testing */

== Introduction ==
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities to manage peer reviews in coursework. Expertiza is built on Ruby on Rails platform. It uses the mysql db as the backend datatbase. More information on Expertiza can be found [https://github.com/expertiza/expertiza here]. Experitza is an open source project. The source code can be forked from [https://github.com/expertiza/expertiza github] and cloned for making modifications.

Our main focus in this OSS project was on the Class: controllers/assignment_controller.rb. This controller handles interaction with an instructor who is creating or editing an assignment. Various issues in the assignments controller and the suitable code changes have been explained in the following sections.

== Project Requirements ==
1. Topics tab is non-functional, but should do what the popup menu item “Add/edit signup sheet” does. 
2. Rubrics tab should show “Teammate Review:” option if “Has Teams?” is selected and “Maximum number of members per team” is greater than 0 in General Tab. 
3. The code should retrieve timezonepref of current user in Due dates tab. Also, time/date picker asks a user to specify the hours, minutes, and seconds of a due date. 
:3.1 Use a time/date picker that doesn’t show seconds. 
:3.2 Minutes should be in the step size 5. 
:3.3 Seconds field should not be displayed 
4. Refactoring 
5. Tests for all the functionality mentioned above

== Implementation ==
This section gives brief details of all the implementations done for project E801.
=== Topics Tab ===
The requirement of this implementation was to make topics tab functional. This tab is mainly responsible to display a page where user can create a topic for a assignment and can see already created topics for that assignment.

====Initial Design====
Ideally, when we click on topics tab, it should display what the popup menu item “Add/edit signup sheet” does.
1.Go to Manage->Assignments
2.For a assignment, click on edit signup sheet
However, in main expertiza project, topics tab was non-functional as shown below. To check Topics tab, follow below mentioned steps: 
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Go to “Topics” tab (You will not be able to view existing topics and create new ones)

[[File:Topics-before.png]]

====Modified Design====
In our implemented project, Topics tab shows already existing topics for an assignment and link to create a new topic where a user can create a new topic. This is similar to popup menu item “Add/edit signup sheet”.
One can follow the same steps as mentioned above to view the functionality:
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Go to “Topics” tab (You should be able to view existing topics and create new ones)
 
[[File:topics-after.png]]

=== Teammate Review Rubric===
====Initial Design====
While editing or creating an assignment the Teammate Review rubric shows up irrespective of whether the assignment is a team assignment or not. It should ideally only show up if the assignment under consideration has teams.
====Modified Design====
Now, the Teammate Review rubric shows up under the Rubrics tab, only if “Has Teams?” is selected and “Maximum number of members per team” is greater than 0 in General Tab.
 
One can follow the below mentioned steps to view the functionality:
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Click on “General” tab
4.Check “Has teams?” and give “Maximum number of members per team” greater than 0.
5.Save assignment
6.Go to “Rubrics” tab. Check if “Teammate Review:” is present.
7.Repeat the same process with “Has Teams?” unchecked and “Maximum number of members” equal to 0. This will not display “Teammate Review:” in the Rubrics tab.

[[File:teams.png]]

[[File:rubric.png]]

=== Refactoring===
Requirements for this section were centered around the following points:
 1. Renaming set_up method. It does not indicate its functionality.
 2. Refactoring copy method
 3. Fixing spell check issue for "Maximum number of review per team"

====Initial Design====
1. set_up method is badly named. It does not indicate what functionality it implements. This method is present in assignments controller. 
2. "Maximum number of review" under rubrics tab is not spelled correctly. This can be found under :
Manage->Assignments->Edit Assignment->Rubrics
3. "copy" method in assignments controller is too long.

====Modified Design====
1. set_up has been renamed to set_up_assignment_review to better reflect what it actually implements. 
2. "Maximum number of review" has been renamed to "Maximum number of reviews". 
3. "copy" method has been refactored by moving some of its functionality into its respective method copy_assignment_questionnaire. 

=== Timezone Issue ===
====Initial Design====
Time zones are not handled properly in the code. The code should retrieve the Preferred Time Zone of the current user and pre-select it in the time/date picker. Also, the time/date picker asks a user to specify the hours, minutes, and seconds of a due date. Obviously we don’t care about seconds, so it would be nice to use a time/date picker that doesn’t show seconds and minutes are in steps of 5. Also daylight savings time needs to be taken care of.

[[File:Time_zone_before.png]]

====Modified Design====
The above mentioned issues are addressed and can be viewed by following the below mentioned steps:
1.Go to Profile. Set timezone to any new timezone and save it.
2.Go to Manage-> Assignments
3.Click on “Edit Assignment” image for any of the assignments
4.Go to “Due dates” tab. Click on the textfield for “Round 1: Submission”. You can find that it doesn’t show seconds and minutes are in the step size 5, also, in “Time Zone”, it shows the timezone set in the earlier step.

[[File:profile.png]]
[[File:Time_zone.png]]

==Testing==

Capybara DSL was selected for running the tests in this project.

===Configuration===
1) First, add Capybara to your Gemfile:
group :development, :test do
gem 'rspec-rails'
gem 'capybara'
end
Run bundle install

2) In spec/spec_helper.rb, add two require calls for Capybara near the top:
ENV["RAILS_ENV"] ||= 'test'
require File.expand_path("../../config/environment", __FILE__)
require 'rspec/rails'

# Add this to load Capybara integration:
require 'capybara/rspec'
require 'capybara/rails'

3) In spec/spec_helper.rb, add
config.include Capybara::DSL

===Test database===
Prepare the test db as follows
$ rake db:prepare:test
$ rake db:migrate RAILS_ENV=test
$ rake db:test:load
$ rake db:seed RAILS_ENV=test
$ rake db:migrate RAILS_ENV=test

===Tests===
Following are the tests that were written to check the modified code.

Test1 : profile_spec.rb
Assertion : Ensure user can set default timezone

Test2 : due_date_spec.rb
Assertion : User should be able to change due dates

Test3 : topic_spec.rb
Assertion : User should be able to create sign up topics by clicking the topic tab in edit assignment page

==Future work ==
In order to further refactor the assignments_controller.rb
 
:1. No usages for the following methods were found:
::- copy_participants_from_course
::- define_instructor_notification_limit

:2. Following methods can be moved to Model classes but are non-functional(throwing errors) in the existing code itself.
::-associate_assignment_with_course
::-remove_assignment_from_course

:3. Methods that add to and delete from delayed_queue should be in the delayed_queue class.(Part of different project)

== External Links ==
# [https://github.com/expertiza/expertiza Expertiza]
# [https://github.com/vshesha/expertiza/ E801_Expertiza]
# [http://152.46.18.166:3000/ Demo]
# [http://jqueryui.com/datepicker/ Datepicker]
# [http://trentrichardson.com/examples/timepicker/ Timepicker]
# [http://guides.rubyonrails.org/layouts_and_rendering.html Layouts and Rendering in Rails]

CSC/ECE 517 Fall 2013/oss vna

2013-10-29T21:47:45Z

Vshesha: /* Testing */

== Introduction ==
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities to manage peer reviews in coursework. Expertiza is built on Ruby on Rails platform. It uses the mysql db as the backend datatbase. More information on Expertiza can be found [https://github.com/expertiza/expertiza here]. Experitza is an open source project. The source code can be forked from [https://github.com/expertiza/expertiza github] and cloned for making modifications.

Our main focus in this OSS project was on the Class: controllers/assignment_controller.rb. This controller handles interaction with an instructor who is creating or editing an assignment. Various issues in the assignments controller and the suitable code changes have been explained in the following sections.

== Project Requirements ==
1. Topics tab is non-functional, but should do what the popup menu item “Add/edit signup sheet” does. 
2. Rubrics tab should show “Teammate Review:” option if “Has Teams?” is selected and “Maximum number of members per team” is greater than 0 in General Tab. 
3. The code should retrieve timezonepref of current user in Due dates tab. Also, time/date picker asks a user to specify the hours, minutes, and seconds of a due date. 
:3.1 Use a time/date picker that doesn’t show seconds. 
:3.2 Minutes should be in the step size 5. 
:3.3 Seconds field should not be displayed 
4. Refactoring 
5. Tests for all the functionality mentioned above

== Implementation ==
This section gives brief details of all the implementations done for project E801.
=== Topics Tab ===
The requirement of this implementation was to make topics tab functional. This tab is mainly responsible to display a page where user can create a topic for a assignment and can see already created topics for that assignment.

====Initial Design====
Ideally, when we click on topics tab, it should display what the popup menu item “Add/edit signup sheet” does.
1.Go to Manage->Assignments
2.For a assignment, click on edit signup sheet
However, in main expertiza project, topics tab was non-functional as shown below. To check Topics tab, follow below mentioned steps: 
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Go to “Topics” tab (You will not be able to view existing topics and create new ones)

[[File:Topics-before.png]]

====Modified Design====
In our implemented project, Topics tab shows already existing topics for an assignment and link to create a new topic where a user can create a new topic. This is similar to popup menu item “Add/edit signup sheet”.
One can follow the same steps as mentioned above to view the functionality:
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Go to “Topics” tab (You should be able to view existing topics and create new ones)
 
[[File:topics-after.png]]

=== Teammate Review Rubric===
====Initial Design====
While editing or creating an assignment the Teammate Review rubric shows up irrespective of whether the assignment is a team assignment or not. It should ideally only show up if the assignment under consideration has teams.
====Modified Design====
Now, the Teammate Review rubric shows up under the Rubrics tab, only if “Has Teams?” is selected and “Maximum number of members per team” is greater than 0 in General Tab.
 
One can follow the below mentioned steps to view the functionality:
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Click on “General” tab
4.Check “Has teams?” and give “Maximum number of members per team” greater than 0.
5.Save assignment
6.Go to “Rubrics” tab. Check if “Teammate Review:” is present.
7.Repeat the same process with “Has Teams?” unchecked and “Maximum number of members” equal to 0. This will not display “Teammate Review:” in the Rubrics tab.

[[File:teams.png]]

[[File:rubric.png]]

=== Refactoring===
Requirements for this section were centered around the following points:
 1. Renaming set_up method. It does not indicate its functionality.
 2. Refactoring copy method
 3. Fixing spell check issue for "Maximum number of review per team"

====Initial Design====
1. set_up method is badly named. It does not indicate what functionality it implements. This method is present in assignments controller. 
2. "Maximum number of review" under rubrics tab is not spelled correctly. This can be found under :
Manage->Assignments->Edit Assignment->Rubrics
3. "copy" method in assignments controller is too long.

====Modified Design====
1. set_up has been renamed to set_up_assignment_review to better reflect what it actually implements. 
2. "Maximum number of review" has been renamed to "Maximum number of reviews". 
3. "copy" method has been refactored by moving some of its functionality into its respective method copy_assignment_questionnaire. 

=== Timezone Issue ===
====Initial Design====
Time zones are not handled properly in the code. The code should retrieve the Preferred Time Zone of the current user and pre-select it in the time/date picker. Also, the time/date picker asks a user to specify the hours, minutes, and seconds of a due date. Obviously we don’t care about seconds, so it would be nice to use a time/date picker that doesn’t show seconds and minutes are in steps of 5. Also daylight savings time needs to be taken care of.

[[File:Time_zone_before.png]]

====Modified Design====
The above mentioned issues are addressed and can be viewed by following the below mentioned steps:
1.Go to Profile. Set timezone to any new timezone and save it.
2.Go to Manage-> Assignments
3.Click on “Edit Assignment” image for any of the assignments
4.Go to “Due dates” tab. Click on the textfield for “Round 1: Submission”. You can find that it doesn’t show seconds and minutes are in the step size 5, also, in “Time Zone”, it shows the timezone set in the earlier step.

[[File:profile.png]]
[[File:Time_zone.png]]

==Testing==

Capybara DSL was selected for running the tests in this project.

Following are the tests that were written to check the modified code.

===Test1===
Assertion :

==Future work ==
In order to further refactor the assignments_controller.rb
 
:1. No usages for the following methods were found:
::- copy_participants_from_course
::- define_instructor_notification_limit

:2. Following methods can be moved to Model classes but are non-functional(throwing errors) in the existing code itself.
::-associate_assignment_with_course
::-remove_assignment_from_course

:3. Methods that add to and delete from delayed_queue should be in the delayed_queue class.(Part of different project)

== External Links ==
# [https://github.com/expertiza/expertiza Expertiza]
# [https://github.com/vshesha/expertiza/ E801_Expertiza]
# [http://152.46.18.166:3000/ Demo]
# [http://jqueryui.com/datepicker/ Datepicker]
# [http://trentrichardson.com/examples/timepicker/ Timepicker]
# [http://guides.rubyonrails.org/layouts_and_rendering.html Layouts and Rendering in Rails]

CSC/ECE 517 Fall 2013/oss vna

2013-10-29T21:40:10Z

Vshesha: /* Project Requirements */

== Introduction ==
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities to manage peer reviews in coursework. Expertiza is built on Ruby on Rails platform. It uses the mysql db as the backend datatbase. More information on Expertiza can be found [https://github.com/expertiza/expertiza here]. Experitza is an open source project. The source code can be forked from [https://github.com/expertiza/expertiza github] and cloned for making modifications.

Our main focus in this OSS project was on the Class: controllers/assignment_controller.rb. This controller handles interaction with an instructor who is creating or editing an assignment. Various issues in the assignments controller and the suitable code changes have been explained in the following sections.

== Project Requirements ==
1. Topics tab is non-functional, but should do what the popup menu item “Add/edit signup sheet” does. 
2. Rubrics tab should show “Teammate Review:” option if “Has Teams?” is selected and “Maximum number of members per team” is greater than 0 in General Tab. 
3. The code should retrieve timezonepref of current user in Due dates tab. Also, time/date picker asks a user to specify the hours, minutes, and seconds of a due date. 
:3.1 Use a time/date picker that doesn’t show seconds. 
:3.2 Minutes should be in the step size 5. 
:3.3 Seconds field should not be displayed 
4. Refactoring 
5. Tests for all the functionality mentioned above

== Implementation ==
This section gives brief details of all the implementations done for project E801.
=== Topics Tab ===
The requirement of this implementation was to make topics tab functional. This tab is mainly responsible to display a page where user can create a topic for a assignment and can see already created topics for that assignment.

====Initial Design====
Ideally, when we click on topics tab, it should display what the popup menu item “Add/edit signup sheet” does.
1.Go to Manage->Assignments
2.For a assignment, click on edit signup sheet
However, in main expertiza project, topics tab was non-functional as shown below. To check Topics tab, follow below mentioned steps: 
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Go to “Topics” tab (You will not be able to view existing topics and create new ones)

[[File:Topics-before.png]]

====Modified Design====
In our implemented project, Topics tab shows already existing topics for an assignment and link to create a new topic where a user can create a new topic. This is similar to popup menu item “Add/edit signup sheet”.
One can follow the same steps as mentioned above to view the functionality:
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Go to “Topics” tab (You should be able to view existing topics and create new ones)
 
[[File:topics-after.png]]

=== Teammate Review Rubric===
====Initial Design====
While editing or creating an assignment the Teammate Review rubric shows up irrespective of whether the assignment is a team assignment or not. It should ideally only show up if the assignment under consideration has teams.
====Modified Design====
Now, the Teammate Review rubric shows up under the Rubrics tab, only if “Has Teams?” is selected and “Maximum number of members per team” is greater than 0 in General Tab.
 
One can follow the below mentioned steps to view the functionality:
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Click on “General” tab
4.Check “Has teams?” and give “Maximum number of members per team” greater than 0.
5.Save assignment
6.Go to “Rubrics” tab. Check if “Teammate Review:” is present.
7.Repeat the same process with “Has Teams?” unchecked and “Maximum number of members” equal to 0. This will not display “Teammate Review:” in the Rubrics tab.

[[File:teams.png]]

[[File:rubric.png]]

=== Refactoring===
Requirements for this section were centered around the following points:
 1. Renaming set_up method. It does not indicate its functionality.
 2. Refactoring copy method
 3. Fixing spell check issue for "Maximum number of review per team"

====Initial Design====
1. set_up method is badly named. It does not indicate what functionality it implements. This method is present in assignments controller. 
2. "Maximum number of review" under rubrics tab is not spelled correctly. This can be found under :
Manage->Assignments->Edit Assignment->Rubrics
3. "copy" method in assignments controller is too long.

====Modified Design====
1. set_up has been renamed to set_up_assignment_review to better reflect what it actually implements. 
2. "Maximum number of review" has been renamed to "Maximum number of reviews". 
3. "copy" method has been refactored by moving some of its functionality into its respective method copy_assignment_questionnaire. 

=== Timezone Issue ===
====Initial Design====
Time zones are not handled properly in the code. The code should retrieve the Preferred Time Zone of the current user and pre-select it in the time/date picker. Also, the time/date picker asks a user to specify the hours, minutes, and seconds of a due date. Obviously we don’t care about seconds, so it would be nice to use a time/date picker that doesn’t show seconds and minutes are in steps of 5. Also daylight savings time needs to be taken care of.

[[File:Time_zone_before.png]]

====Modified Design====
The above mentioned issues are addressed and can be viewed by following the below mentioned steps:
1.Go to Profile. Set timezone to any new timezone and save it.
2.Go to Manage-> Assignments
3.Click on “Edit Assignment” image for any of the assignments
4.Go to “Due dates” tab. Click on the textfield for “Round 1: Submission”. You can find that it doesn’t show seconds and minutes are in the step size 5, also, in “Time Zone”, it shows the timezone set in the earlier step.

[[File:profile.png]]
[[File:Time_zone.png]]

==Testing==
The testing was limited to the changes made as part of this project.

Following test

==Future work ==
In order to further refactor the assignments_controller.rb
 
:1. No usages for the following methods were found:
::- copy_participants_from_course
::- define_instructor_notification_limit

:2. Following methods can be moved to Model classes but are non-functional(throwing errors) in the existing code itself.
::-associate_assignment_with_course
::-remove_assignment_from_course

:3. Methods that add to and delete from delayed_queue should be in the delayed_queue class.(Part of different project)

== External Links ==
# [https://github.com/expertiza/expertiza Expertiza]
# [https://github.com/vshesha/expertiza/ E801_Expertiza]
# [http://152.46.18.166:3000/ Demo]
# [http://jqueryui.com/datepicker/ Datepicker]
# [http://trentrichardson.com/examples/timepicker/ Timepicker]
# [http://guides.rubyonrails.org/layouts_and_rendering.html Layouts and Rendering in Rails]

CSC/ECE 517 Fall 2013/oss vna

2013-10-29T21:38:45Z

Vshesha: /* Introduction */

== Introduction ==
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities to manage peer reviews in coursework. Expertiza is built on Ruby on Rails platform. It uses the mysql db as the backend datatbase. More information on Expertiza can be found [https://github.com/expertiza/expertiza here]. Experitza is an open source project. The source code can be forked from [https://github.com/expertiza/expertiza github] and cloned for making modifications.

Our main focus in this OSS project was on the Class: controllers/assignment_controller.rb. This controller handles interaction with an instructor who is creating or editing an assignment. Various issues in the assignments controller and the suitable code changes have been explained in the following sections.

== Project Requirements ==
1. Topics tab is non-functional, but should do what the popup menu item “Add/edit signup sheet” does. 
2. Rubrics tab should show “Teammate Review:” option if “Has Teams?” is selected and “Maximum number of members per team” is greater than 0 in General Tab. 
3. The code should retrieve timezonepref of current user in Due dates tab. Also, time/date picker asks a user to specify the hours, minutes, and seconds of a due date. 
:3.1 Use a time/date picker that doesn’t show seconds. 
:3.2 Minutes should be in the step size 5. 
4. Refactoring 
5. Tests for all the functionality mentioned above

== Implementation ==
This section gives brief details of all the implementations done for project E801.
=== Topics Tab ===
The requirement of this implementation was to make topics tab functional. This tab is mainly responsible to display a page where user can create a topic for a assignment and can see already created topics for that assignment.

====Initial Design====
Ideally, when we click on topics tab, it should display what the popup menu item “Add/edit signup sheet” does.
1.Go to Manage->Assignments
2.For a assignment, click on edit signup sheet
However, in main expertiza project, topics tab was non-functional as shown below. To check Topics tab, follow below mentioned steps: 
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Go to “Topics” tab (You will not be able to view existing topics and create new ones)

[[File:Topics-before.png]]

====Modified Design====
In our implemented project, Topics tab shows already existing topics for an assignment and link to create a new topic where a user can create a new topic. This is similar to popup menu item “Add/edit signup sheet”.
One can follow the same steps as mentioned above to view the functionality:
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Go to “Topics” tab (You should be able to view existing topics and create new ones)
 
[[File:topics-after.png]]

=== Teammate Review Rubric===
====Initial Design====
While editing or creating an assignment the Teammate Review rubric shows up irrespective of whether the assignment is a team assignment or not. It should ideally only show up if the assignment under consideration has teams.
====Modified Design====
Now, the Teammate Review rubric shows up under the Rubrics tab, only if “Has Teams?” is selected and “Maximum number of members per team” is greater than 0 in General Tab.
 
One can follow the below mentioned steps to view the functionality:
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Click on “General” tab
4.Check “Has teams?” and give “Maximum number of members per team” greater than 0.
5.Save assignment
6.Go to “Rubrics” tab. Check if “Teammate Review:” is present.
7.Repeat the same process with “Has Teams?” unchecked and “Maximum number of members” equal to 0. This will not display “Teammate Review:” in the Rubrics tab.

[[File:teams.png]]

[[File:rubric.png]]

=== Refactoring===
Requirements for this section were centered around the following points:
 1. Renaming set_up method. It does not indicate its functionality.
 2. Refactoring copy method
 3. Fixing spell check issue for "Maximum number of review per team"

====Initial Design====
1. set_up method is badly named. It does not indicate what functionality it implements. This method is present in assignments controller. 
2. "Maximum number of review" under rubrics tab is not spelled correctly. This can be found under :
Manage->Assignments->Edit Assignment->Rubrics
3. "copy" method in assignments controller is too long.

====Modified Design====
1. set_up has been renamed to set_up_assignment_review to better reflect what it actually implements. 
2. "Maximum number of review" has been renamed to "Maximum number of reviews". 
3. "copy" method has been refactored by moving some of its functionality into its respective method copy_assignment_questionnaire. 

=== Timezone Issue ===
====Initial Design====
Time zones are not handled properly in the code. The code should retrieve the Preferred Time Zone of the current user and pre-select it in the time/date picker. Also, the time/date picker asks a user to specify the hours, minutes, and seconds of a due date. Obviously we don’t care about seconds, so it would be nice to use a time/date picker that doesn’t show seconds and minutes are in steps of 5. Also daylight savings time needs to be taken care of.

[[File:Time_zone_before.png]]

====Modified Design====
The above mentioned issues are addressed and can be viewed by following the below mentioned steps:
1.Go to Profile. Set timezone to any new timezone and save it.
2.Go to Manage-> Assignments
3.Click on “Edit Assignment” image for any of the assignments
4.Go to “Due dates” tab. Click on the textfield for “Round 1: Submission”. You can find that it doesn’t show seconds and minutes are in the step size 5, also, in “Time Zone”, it shows the timezone set in the earlier step.

[[File:profile.png]]
[[File:Time_zone.png]]

==Testing==
The testing was limited to the changes made as part of this project.

Following test

==Future work ==
In order to further refactor the assignments_controller.rb
 
:1. No usages for the following methods were found:
::- copy_participants_from_course
::- define_instructor_notification_limit

:2. Following methods can be moved to Model classes but are non-functional(throwing errors) in the existing code itself.
::-associate_assignment_with_course
::-remove_assignment_from_course

:3. Methods that add to and delete from delayed_queue should be in the delayed_queue class.(Part of different project)

== External Links ==
# [https://github.com/expertiza/expertiza Expertiza]
# [https://github.com/vshesha/expertiza/ E801_Expertiza]
# [http://152.46.18.166:3000/ Demo]
# [http://jqueryui.com/datepicker/ Datepicker]
# [http://trentrichardson.com/examples/timepicker/ Timepicker]
# [http://guides.rubyonrails.org/layouts_and_rendering.html Layouts and Rendering in Rails]

CSC/ECE 517 Fall 2013/oss vna

2013-10-29T21:38:30Z

Vshesha: /* Introduction */

== Introduction ==
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities to manage peer reviews in coursework.

Expertiza is built on Ruby on Rails platform. It uses the mysql db as the backend datatbase. More information on Expertiza can be found [https://github.com/expertiza/expertiza here]. Experitza is an open source project. The source code can be forked from [https://github.com/expertiza/expertiza github] and cloned for making modifications.

Our main focus in this OSS project was on the Class: controllers/assignment_controller.rb. This controller handles interaction with an instructor who is creating or editing an assignment.

Various issues in the assignments controller and the suitable code changes have been explained in the following sections.

== Project Requirements ==
1. Topics tab is non-functional, but should do what the popup menu item “Add/edit signup sheet” does. 
2. Rubrics tab should show “Teammate Review:” option if “Has Teams?” is selected and “Maximum number of members per team” is greater than 0 in General Tab. 
3. The code should retrieve timezonepref of current user in Due dates tab. Also, time/date picker asks a user to specify the hours, minutes, and seconds of a due date. 
:3.1 Use a time/date picker that doesn’t show seconds. 
:3.2 Minutes should be in the step size 5. 
4. Refactoring 
5. Tests for all the functionality mentioned above

== Implementation ==
This section gives brief details of all the implementations done for project E801.
=== Topics Tab ===
The requirement of this implementation was to make topics tab functional. This tab is mainly responsible to display a page where user can create a topic for a assignment and can see already created topics for that assignment.

====Initial Design====
Ideally, when we click on topics tab, it should display what the popup menu item “Add/edit signup sheet” does.
1.Go to Manage->Assignments
2.For a assignment, click on edit signup sheet
However, in main expertiza project, topics tab was non-functional as shown below. To check Topics tab, follow below mentioned steps: 
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Go to “Topics” tab (You will not be able to view existing topics and create new ones)

[[File:Topics-before.png]]

====Modified Design====
In our implemented project, Topics tab shows already existing topics for an assignment and link to create a new topic where a user can create a new topic. This is similar to popup menu item “Add/edit signup sheet”.
One can follow the same steps as mentioned above to view the functionality:
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Go to “Topics” tab (You should be able to view existing topics and create new ones)
 
[[File:topics-after.png]]

=== Teammate Review Rubric===
====Initial Design====
While editing or creating an assignment the Teammate Review rubric shows up irrespective of whether the assignment is a team assignment or not. It should ideally only show up if the assignment under consideration has teams.
====Modified Design====
Now, the Teammate Review rubric shows up under the Rubrics tab, only if “Has Teams?” is selected and “Maximum number of members per team” is greater than 0 in General Tab.
 
One can follow the below mentioned steps to view the functionality:
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Click on “General” tab
4.Check “Has teams?” and give “Maximum number of members per team” greater than 0.
5.Save assignment
6.Go to “Rubrics” tab. Check if “Teammate Review:” is present.
7.Repeat the same process with “Has Teams?” unchecked and “Maximum number of members” equal to 0. This will not display “Teammate Review:” in the Rubrics tab.

[[File:teams.png]]

[[File:rubric.png]]

=== Refactoring===
Requirements for this section were centered around the following points:
 1. Renaming set_up method. It does not indicate its functionality.
 2. Refactoring copy method
 3. Fixing spell check issue for "Maximum number of review per team"

====Initial Design====
1. set_up method is badly named. It does not indicate what functionality it implements. This method is present in assignments controller. 
2. "Maximum number of review" under rubrics tab is not spelled correctly. This can be found under :
Manage->Assignments->Edit Assignment->Rubrics
3. "copy" method in assignments controller is too long.

====Modified Design====
1. set_up has been renamed to set_up_assignment_review to better reflect what it actually implements. 
2. "Maximum number of review" has been renamed to "Maximum number of reviews". 
3. "copy" method has been refactored by moving some of its functionality into its respective method copy_assignment_questionnaire. 

=== Timezone Issue ===
====Initial Design====
Time zones are not handled properly in the code. The code should retrieve the Preferred Time Zone of the current user and pre-select it in the time/date picker. Also, the time/date picker asks a user to specify the hours, minutes, and seconds of a due date. Obviously we don’t care about seconds, so it would be nice to use a time/date picker that doesn’t show seconds and minutes are in steps of 5. Also daylight savings time needs to be taken care of.

[[File:Time_zone_before.png]]

====Modified Design====
The above mentioned issues are addressed and can be viewed by following the below mentioned steps:
1.Go to Profile. Set timezone to any new timezone and save it.
2.Go to Manage-> Assignments
3.Click on “Edit Assignment” image for any of the assignments
4.Go to “Due dates” tab. Click on the textfield for “Round 1: Submission”. You can find that it doesn’t show seconds and minutes are in the step size 5, also, in “Time Zone”, it shows the timezone set in the earlier step.

[[File:profile.png]]
[[File:Time_zone.png]]

==Testing==
The testing was limited to the changes made as part of this project.

Following test

==Future work ==
In order to further refactor the assignments_controller.rb
 
:1. No usages for the following methods were found:
::- copy_participants_from_course
::- define_instructor_notification_limit

:2. Following methods can be moved to Model classes but are non-functional(throwing errors) in the existing code itself.
::-associate_assignment_with_course
::-remove_assignment_from_course

:3. Methods that add to and delete from delayed_queue should be in the delayed_queue class.(Part of different project)

== External Links ==
# [https://github.com/expertiza/expertiza Expertiza]
# [https://github.com/vshesha/expertiza/ E801_Expertiza]
# [http://152.46.18.166:3000/ Demo]
# [http://jqueryui.com/datepicker/ Datepicker]
# [http://trentrichardson.com/examples/timepicker/ Timepicker]
# [http://guides.rubyonrails.org/layouts_and_rendering.html Layouts and Rendering in Rails]

CSC/ECE 517 Fall 2013/oss vna

2013-10-29T21:37:38Z

Vshesha: /* Introduction */

== Introduction ==
Expertiza is a web application where students can submit and peer-review learning objects (articles, code, web sites, etc). It is used in select courses at NC State and by professors at several other colleges and universities to manage peer reviews in coursework.

Expertiza is built on Ruby on Rails platform. It uses the mysql db as the backend datatbase. More information on Expertiza can be found [https://github.com/expertiza/expertiza here]. Experitza is an open source project. The source code can be forked from [https://github.com/expertiza/expertiza github] and cloned for making modifications.

Our main focus in this OSS project was on the Class: controllers/assignment_controller.rb. This controller handles interaction with an instructor who is creating or editing an assigment. Various issues in the controller and the suitable code changes have been explained in the following sections.

== Project Requirements ==
1. Topics tab is non-functional, but should do what the popup menu item “Add/edit signup sheet” does. 
2. Rubrics tab should show “Teammate Review:” option if “Has Teams?” is selected and “Maximum number of members per team” is greater than 0 in General Tab. 
3. The code should retrieve timezonepref of current user in Due dates tab. Also, time/date picker asks a user to specify the hours, minutes, and seconds of a due date. 
:3.1 Use a time/date picker that doesn’t show seconds. 
:3.2 Minutes should be in the step size 5. 
4. Refactoring 
5. Tests for all the functionality mentioned above

== Implementation ==
This section gives brief details of all the implementations done for project E801.
=== Topics Tab ===
The requirement of this implementation was to make topics tab functional. This tab is mainly responsible to display a page where user can create a topic for a assignment and can see already created topics for that assignment.

====Initial Design====
Ideally, when we click on topics tab, it should display what the popup menu item “Add/edit signup sheet” does.
1.Go to Manage->Assignments
2.For a assignment, click on edit signup sheet
However, in main expertiza project, topics tab was non-functional as shown below. To check Topics tab, follow below mentioned steps: 
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Go to “Topics” tab (You will not be able to view existing topics and create new ones)

[[File:Topics-before.png]]

====Modified Design====
In our implemented project, Topics tab shows already existing topics for an assignment and link to create a new topic where a user can create a new topic. This is similar to popup menu item “Add/edit signup sheet”.
One can follow the same steps as mentioned above to view the functionality:
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Go to “Topics” tab (You should be able to view existing topics and create new ones)
 
[[File:topics-after.png]]

=== Teammate Review Rubric===
====Initial Design====
While editing or creating an assignment the Teammate Review rubric shows up irrespective of whether the assignment is a team assignment or not. It should ideally only show up if the assignment under consideration has teams.
====Modified Design====
Now, the Teammate Review rubric shows up under the Rubrics tab, only if “Has Teams?” is selected and “Maximum number of members per team” is greater than 0 in General Tab.
 
One can follow the below mentioned steps to view the functionality:
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Click on “General” tab
4.Check “Has teams?” and give “Maximum number of members per team” greater than 0.
5.Save assignment
6.Go to “Rubrics” tab. Check if “Teammate Review:” is present.
7.Repeat the same process with “Has Teams?” unchecked and “Maximum number of members” equal to 0. This will not display “Teammate Review:” in the Rubrics tab.

[[File:teams.png]]

[[File:rubric.png]]

=== Refactoring===
Requirements for this section were centered around the following points:
 1. Renaming set_up method. It does not indicate its functionality.
 2. Refactoring copy method
 3. Fixing spell check issue for "Maximum number of review per team"

====Initial Design====
1. set_up method is badly named. It does not indicate what functionality it implements. This method is present in assignments controller. 
2. "Maximum number of review" under rubrics tab is not spelled correctly. This can be found under :
Manage->Assignments->Edit Assignment->Rubrics
3. "copy" method in assignments controller is too long.

====Modified Design====
1. set_up has been renamed to set_up_assignment_review to better reflect what it actually implements. 
2. "Maximum number of review" has been renamed to "Maximum number of reviews". 
3. "copy" method has been refactored by moving some of its functionality into its respective method copy_assignment_questionnaire. 

=== Timezone Issue ===
====Initial Design====
Time zones are not handled properly in the code. The code should retrieve the Preferred Time Zone of the current user and pre-select it in the time/date picker. Also, the time/date picker asks a user to specify the hours, minutes, and seconds of a due date. Obviously we don’t care about seconds, so it would be nice to use a time/date picker that doesn’t show seconds and minutes are in steps of 5. Also daylight savings time needs to be taken care of.

[[File:Time_zone_before.png]]

====Modified Design====
The above mentioned issues are addressed and can be viewed by following the below mentioned steps:
1.Go to Profile. Set timezone to any new timezone and save it.
2.Go to Manage-> Assignments
3.Click on “Edit Assignment” image for any of the assignments
4.Go to “Due dates” tab. Click on the textfield for “Round 1: Submission”. You can find that it doesn’t show seconds and minutes are in the step size 5, also, in “Time Zone”, it shows the timezone set in the earlier step.

[[File:profile.png]]
[[File:Time_zone.png]]

==Testing==
The testing was limited to the changes made as part of this project.

Following test

==Future work ==
In order to further refactor the assignments_controller.rb
 
:1. No usages for the following methods were found:
::- copy_participants_from_course
::- define_instructor_notification_limit

:2. Following methods can be moved to Model classes but are non-functional(throwing errors) in the existing code itself.
::-associate_assignment_with_course
::-remove_assignment_from_course

:3. Methods that add to and delete from delayed_queue should be in the delayed_queue class.(Part of different project)

== External Links ==
# [https://github.com/expertiza/expertiza Expertiza]
# [https://github.com/vshesha/expertiza/ E801_Expertiza]
# [http://152.46.18.166:3000/ Demo]
# [http://jqueryui.com/datepicker/ Datepicker]
# [http://trentrichardson.com/examples/timepicker/ Timepicker]
# [http://guides.rubyonrails.org/layouts_and_rendering.html Layouts and Rendering in Rails]

CSC/ECE 517 Fall 2013/oss vna

2013-10-29T21:35:10Z

Vshesha: /* Introduction */

CSC/ECE 517 Fall 2013/oss vna

2013-10-29T21:33:31Z

Vshesha: /* Introduction */

CSC/ECE 517 Fall 2013/oss vna

2013-10-29T21:32:22Z

Vshesha: /* Introduction */

CSC/ECE 517 Fall 2013/oss vna

2013-10-29T21:27:49Z

Vshesha: /* Introduction */

CSC/ECE 517 Fall 2013/oss vna

2013-10-29T21:22:42Z

Vshesha: /* Testing */

== Introduction ==
== Project Requirements ==
1. Topics tab is non-functional, but should do what the popup menu item “Add/edit signup sheet” does. 
2. Rubrics tab should show “Teammate Review:” option if “Has Teams?” is selected and “Maximum number of members per team” is greater than 0 in General Tab. 
3. The code should retrieve timezonepref of current user in Due dates tab. Also, time/date picker asks a user to specify the hours, minutes, and seconds of a due date. 
:3.1 Use a time/date picker that doesn’t show seconds. 
:3.2 Minutes should be in the step size 5. 
4. Refactoring 
5. Tests for all the functionality mentioned above

== Implementation ==
This section gives brief details of all the implementations done for project E801.
=== Topics Tab ===
The requirement of this implementation was to make topics tab functional. This tab is mainly responsible to display a page where user can create a topic for a assignment and can see already created topics for that assignment.

====Initial Design====
Ideally, when we click on topics tab, it should display what the popup menu item “Add/edit signup sheet” does.
1.Go to Manage->Assignments
2.For a assignment, click on edit signup sheet
However, in main expertiza project, topics tab was non-functional as shown below. To check Topics tab, follow below mentioned steps: 
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Go to “Topics” tab (You will not be able to view existing topics and create new ones)

[[File:Topics-before.png]]

====Modified Design====
In our implemented project, Topics tab shows already existing topics for an assignment and link to create a new topic where a user can create a new topic. This is similar to popup menu item “Add/edit signup sheet”.
One can follow the same steps as mentioned above to view the functionality:
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Go to “Topics” tab (You should be able to view existing topics and create new ones)
 
[[File:topics-after.png]]

=== Teammate Review Rubric===
====Initial Design====
While editing or creating an assignment the Teammate Review rubric shows up irrespective of whether the assignment is a team assignment or not. It should ideally only show up if the assignment under consideration has teams.
====Modified Design====
Now, the Teammate Review rubric shows up under the Rubrics tab, only if “Has Teams?” is selected and “Maximum number of members per team” is greater than 0 in General Tab.
 
One can follow the below mentioned steps to view the functionality:
1.Go to Manage-> Assignments
2.Click on “edit assignment” image for any of the assignments
3.Click on “General” tab
4.Check “Has teams?” and give “Maximum number of members per team” greater than 0.
5.Save assignment
6.Go to “Rubrics” tab. Check if “Teammate Review:” is present.
7.Repeat the same process with “Has Teams?” unchecked and “Maximum number of members” equal to 0. This will not display “Teammate Review:” in the Rubrics tab.

[[File:teams.png]]

[[File:rubric.png]]

=== Refactoring===
Requirements for this section were centered around the following points:
 1. Renaming set_up method. It does not indicate its functionality.
 2. Refactoring copy method
 3. Fixing spell check issue for "Maximum number of review per team"

====Initial Design====
1. set_up method is badly named. It does not indicate what functionality it implements. This method is present in assignments controller. 
2. "Maximum number of review" under rubrics tab is not spelled correctly. This can be found under :
Manage->Assignments->Edit Assignment->Rubrics
3. "copy" method in assignments controller is too long.

====Modified Design====
1. set_up has been renamed to set_up_assignment_review to better reflect what it actually implements. 
2. "Maximum number of review" has been renamed to "Maximum number of reviews". 
3. "copy" method has been refactored by moving some of its functionality into its respective method copy_assignment_questionnaire. 

=== Timezone Issue ===
====Initial Design====
Time zones are not handled properly in the code. The code should retrieve the Preferred Time Zone of the current user and pre-select it in the time/date picker. Also, the time/date picker asks a user to specify the hours, minutes, and seconds of a due date. Obviously we don’t care about seconds, so it would be nice to use a time/date picker that doesn’t show seconds and minutes are in steps of 5. Also daylight savings time needs to be taken care of.

[[File:Time_zone_before.png]]

====Modified Design====
The above mentioned issues are addressed and can be viewed by following the below mentioned steps:
1.Go to Profile. Set timezone to any new timezone and save it.
2.Go to Manage-> Assignments
3.Click on “Edit Assignment” image for any of the assignments
4.Go to “Due dates” tab. Click on the textfield for “Round 1: Submission”. You can find that it doesn’t show seconds and minutes are in the step size 5, also, in “Time Zone”, it shows the timezone set in the earlier step.

[[File:profile.png]]
[[File:Time_zone.png]]

==Testing==
The testing was limited to the changes made as part of this project.

Following test

==Future work ==
In order to further refactor the assignments_controller.rb
 
:1. No usages for the following methods were found:
::- copy_participants_from_course
::- define_instructor_notification_limit

:2. Following methods can be moved to Model classes but are non-functional(throwing errors) in the existing code itself.
::-associate_assignment_with_course
::-remove_assignment_from_course

:3. Methods that add to and delete from delayed_queue should be in the delayed_queue class.(Part of different project)

== External Links ==
# [https://github.com/expertiza/expertiza Expertiza]
# [https://github.com/vshesha/expertiza/ E801_Expertiza]
# [http://152.46.18.166:3000/ Demo]
# [http://jqueryui.com/datepicker/ Datepicker]
# [http://trentrichardson.com/examples/timepicker/ Timepicker]
# [http://guides.rubyonrails.org/layouts_and_rendering.html Layouts and Rendering in Rails]

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-15T03:00:38Z

Vshesha: /* Headline text */

[[File:Browsers.png|frame|alt=Puzzle globe|GUI Testing]]
'''Open Source GUI Testing Tools'''

Graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its designed specifications.

GUI testing is difficult mainly due to following reasons :
* Large space of possibilities. Each sequence of GUI commands can result in various states. Evaluation of all these states is essential for validation of the GUI of the given software.
*[http://en.wikipedia.org/wiki/Event-driven_architecture Event-driven architecture]. The test suite has to simulate the various user created actions.

Following are the challenges encountered while testing the graphical user interface of any software or system:
* Automation is difficult.
* The scope for testing is enormous
* Inability to determine the state of the program from GUI.
* [http://en.wikipedia.org/wiki/Regression_testing Regression testing] is difficult. Testcases may not be reusable

The current trend in user interfaces is geared towards graphical user interfaces (GUIs). This presents a problem for designing tests for software, since GUIs are very complex and hence GUI testing is very time consuming. Automation is a requirement for testing any larger graphical user interfaces, but automating GUI tests is not a straightforward task. Techniques which are familiar from the command line interface (CLI) age, don’t translate to the GUI world without problems.

==Test Automation==

The advantages of test automation are as follows.
*Frequent regression testing
*Rapid feedback to developers - The earlier the problems are found, the cheaper it is to fix them. An automated unit test suite finds problems effectively as early as possible, long before the software reaches a customer, and even before it reaches the QA team.
*Virtually unlimited iterations of test case execution
*Support for Agile and extreme development methodologies
*Disciplined documentation of test cases
*Customized defect reporting
*Finding defects missed by manual testing

The challenge is in extending these advantages to GUI testing.

==GUI testing in Ruby and Rails==

Ruby prefers the term scripted testing over the more traditional automated testing. For testing a GUI application there can be several kind of tests in the background to verify the functionality and requirements of an application.

Various frameworks that support testing in Ruby are:
* Test:Unit - It is a unit testing framework for Ruby.
* Capybara[https://github.com/jnicklas/capybara] - It is an integration testing tool for web applications.
* Rspec[http://rspec.info/] - Behaviour Driven Development (BDD) framework/ test tool
* Cucumber[https://github.com/cucumber/cucumber] - It is a tool for running automated acceptance tests written in a behavior-driven development (BDD) style

Ruby on Rails testing frameworks are much more advanced than other web frameworks.

==GUI Testing - Pitfalls==
*Coverage criteria cannot be determined accurately with GUI testing.
*Verifying whether the GUI test executes correctly poses a problem as the logging is difficult.
*Developing a stable regression suite is difficult since simple changes in GUI can render the test suite obsolete.

==GUI Testing Tools==

GUI testing tools serve the purpose of automating the testing process of software with graphical user interfaces. Following are few of the available open source GUI testing tools:

*AutoHotkey
*CubicTest
*Dogtail
*Dojo
*Selenium
*Watir
*GNU Xnee
*Sikuli
*Webrat

==Selenium==

===Introduction===
Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language (Selenium IDE). It also provides a test domain-specific language (Selenese) to write tests in a number of popular programming languages, including Java, C#, [http://groovy.codehaus.org/ Groovy], Perl, PHP, Python and Ruby. The tests can then be run against most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.

===Selenium Tool Suite===
Selenium is composed of multiple software tools.

====Selenium IDE====
*Prototyping tool for building testscripts.
*Firefox plugin provides easy to use interface for developing automated tests.
*Supports 'record and play' feature to create reusable scripts for testing.

====Selenium1====
*Also known as Selenium RC or Remote Control
*Provides flexibility in porting tests across browsers and platforms.
*Currently in maintainence mode. No active development.

====Selenium 2====
*Also known as Selenium Webdriver
*Supports WebDriver API thus providing maximum flexibility in porting the tests.
*Runs Selenium 1’s Selenium RC interface for backwards compatibility.

====Selenium Grid====
*Selenium-Grid allows the Selenium RC solution to scale for large test suites and for test suites that must be run in multiple environments.
*Selenium Grid runs the tests in parallel, that is, different tests can be run at the same time on different remote machines.
*Selenium Grid greatly improves the time it takes to run the suite by making use of parallel processing.

===Supported Browsers and Platforms===

====Selenium 2====
*Google Chrome 12.0.712.0+
*Internet Explorer 6, 7, 8, 9 - 32 and 64-bit where applicable
*Firefox 3.0, 3.5, 3.6, 4.0, 5.0, 6, 7
*Opera 11.5+
*HtmlUnit 2.9
*Android – 2.3+ for phones and tablets (devices & emulators)
*iOS 3+ for phones (devices & emulators) and 3.2+ for tablets (devices & emulators)

====Selenium 1 and Selenium IDE====
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Browser'''
| align="center" style="background:#f0f0f0;"|'''Selenium IDE'''
| align="center" style="background:#f0f0f0;"|'''Selenium 1 (RC)'''
| align="center" style="background:#f0f0f0;"|'''Operating Systems'''
|-
| Firefox 2, 3||Record and playback tests ||Start browser, run tests||Windows, Linux, Mac
|-
| IE 6, 7, 8||Unsupported ||Start browser, run tests||Windows
|-
| Safari 2, 3, 4||Unsupported ||Start browser, run tests||Windows, Mac
|-
| Opera 8, 9, 10||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
| Google Chrome||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
|}

===Advantages===
The chief advantages of Selenium are :
*Flexibility - Test automation can be customized by adding functionality to Selenium test scripts and Selenium framework.
*Open Source - The source code can be downloaded and modified as needed to suit new browsers.
*Deploys on multiple paltforms - Windows, Linux, and Macintosh.

===Disadvantages===
*Identifying the locators and common attributes like id, names etc as well as XPATH, javascript DOM and others is difficult.
*Results are not available in good detail. Debugging failures migt prove to be difficult sometimes.
*Loop and data driven testing is not supported by Selenium IDE.
*Options to verify the images are not available.

==Auto Hot Key==
AutoHotkey automates tests by sending keystrokes and mouse clicks to the target application with the help of a macro recorder.
Virtually any key, button, or combination can become a hotkey.
Following are the notable features of hotkey:
* Expand abbreviations as you type them. For example, typing "gn" can automatically produce "good night".
* Create custom data-entry forms, user interfaces, and menu bars.
* Remap keys and buttons on your keyboard, joystick, and mouse.
* Convert any script into an EXE file that can be run on computers that don't have AutoHotkey installed.

Quick start tutorial : http://www.autohotkey.com/docs/Tutorial.htm

==Watir==
Watir, pronounced water, stands for Web Application Testing in Ruby. Watir is an open-source (BSD) family of Ruby libraries for automating web browsers. It is distributed as a Ruby GEM named 'Watir'. Watir drives browsers the same way people do. It clicks links, fills in forms, presses buttons. Watir also checks results, such as whether expected text appears on the page or not.

There are 2 version available :
* Watir-Classic : supports only Internet Explorer on Windows
* Watir-WebDriver : supports Chrome, Firefox, Internet Explorer, Opera and also running in headless mode (HTMLUnit).

==GNU Xnee==
GNU Xnee is a suite of programs that can record, replay and distribute user actions under the X11 environment. Xnee has the capability to :
* Automate tests like nightly regression
* Demonstrate programs by recording and replaying a user interaction with the system
* Distribute actions from system admin to end users.

The Record and replay ‘macro’ is the highlight of Xnee.

==DOJO==
Dojo is a JavaScript framework targeting the many needs of large-scale client-side web development.

* Dojo abstracts the differences among diverse browsers to provide APIs that will work on all of them (it can even run on the server under Node.js)
* It establishes a framework for defining modules of code and managing their inter-dependencies
* Supports internationalization, localization, and accessibility
* Provides a rich suite of commonly needed utility classes and user-interface widgets.

==CubicTest==
CubicTest is a graphical Eclipse plug-in for writing Selenium and Watir tests. It makes tests faster and easier to write, and provides abstractions to make tests more robust and reusable.

* CubicTest's test editor is centered around pages/states and transitions between these pages/states.
* The model is intuitive for both Ajax and traditional web applications and supports most user interaction types.
* CubicTest features an innovative test recorder and test runner based on Selenium RC which are fully integrated with the graphical test editor.

==Dogtail==
Dogtail is a GUI test tool and automation framework written in Python. It uses Accessibility (a11y) technologies to communicate with desktop applications. Dogtail scripts are written in Python and executed like any other Python program.
Follwoing are the notable features of Dogtail:
* Object-Oriented API: With the object oriented API, you are under control of the UI tree and its elements, allowing you to write sophisticated scripts utilizing benefits of OO right deep from dogtail.
* Procedural API: Ace programmer credentials are not necessary to write useful automated scripts with procedural API.
* Easily Extensible: Writing custom classes and helper libraries are easy.
* Results and debug reporting: Separate logs for test case comparisons and debug information are generated.

==Sikuli==
Sikuli automates GUI testing by using image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code.
* Sikuli uses an innovative approach of automating GUI tests by using screenshots and powerpoint slides.
* Sikuli Script is a visual scripting API using [http://en.wikipedia.org/wiki/Jython Jython] to create automation scripts.
* Sikuli includes an integrated development environment (IDE) for writing visual Sikuli scripts with screenshots.

==Webrat==
Webrat lets you quickly write expressive and robust acceptance tests for a Ruby web application.

==See Also==
* Web testing tools [http://en.wikipedia.org/wiki/List_of_web_testing_tools]
* Selenium Framework [http://www.mediawiki.org/wiki/Selenium_Framework]
* Selenium [http://www.jroller.com/selenium/]
* Using Selenium [http://aspyct.org/blog/2012/09/09/functional-web-testing-with-selenium-and-ruby/]
* Selenium by example [http://learnseleniumautomation.blogspot.in/2012/08/learn-selenium-webdriver-by-example.html]
* Scalable UI Testing with Selenium [http://jeffmw.com/2012/05/28/scalable-ui-testing-with-selenium/]

==References==
*http://docs.seleniumhq.org/docs/
*http://www.eecs.yorku.ca/course_archive/2004-05/W/4313/Slides/Module10-GUI.pdf - 2004-05
*http://www.cs.helsinki.fi/u/paakki/mikkolainen.pdf
*http://watir.com/
*http://www.gnu.org/software/xnee/
*https://fedorahosted.org/dogtail/
*http://www.cubictest.org/
*http://www.autohotkey.com/
*http://www.sikuli.org/
*http://sivaeluri.blogspot.com/2012/08/advantages-and-disadvantages-of.html
*http://dojotoolkit.org/reference-guide/1.9/util/dohrobot.html
*''GUI Testing: Pitfalls and Process'', Atif M. Memon, University of Maryland, IEEE Computer 2002, p. 87 - 88 [http://cvs.cs.umd.edu/~atif/papers/MemonIEEEComputer2002.pdf ]

==Note to reviewers==
The topic is very vast. Hence the wiki is written based on the guidelines provided by the TA's and the Prof.
* List all GUI tools used in OSS that you can quickly identify.
* Try to describe the tools to the same level of detail, except that you may choose to go into more detail on tools that are used with Rails.
* Listing of commands is not a good idea. You are not writing a reference manual; you are writing a descriptive article that someone might read to learn about what's available before choosing a tool or tools. You should aim for readability.

We have referred the respective tool websites to provide the overview for each one of them. We have provided appropriate citations as well. Additionally the tool and the documentation itself are under GNU/ open source licence and hence will not fall under copyright violation. Please correct us if we are wrong.

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-15T02:49:36Z

Vshesha: /* References */

[[File:Browsers.png|frame|alt=Puzzle globe|GUI Testing]]
'''Open Source GUI Testing Tools'''

Graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its designed specifications.

GUI testing is difficult mainly due to following reasons :
* Large space of possibilities. Each sequence of GUI commands can result in various states. Evaluation of all these states is essential for validation of the GUI of the given software.
*[http://en.wikipedia.org/wiki/Event-driven_architecture Event-driven architecture]. The test suite has to simulate the various user created actions.

Following are the challenges encountered while testing the graphical user interface of any software or system:
* Automation is difficult.
* The scope for testing is enormous
* Inability to determine the state of the program from GUI.
* [http://en.wikipedia.org/wiki/Regression_testing Regression testing] is difficult. Testcases may not be reusable

The current trend in user interfaces is geared towards graphical user interfaces (GUIs). This presents a problem for designing tests for software, since GUIs are very complex and hence GUI testing is very time consuming. Automation is a requirement for testing any larger graphical user interfaces, but automating GUI tests is not a straightforward task. Techniques which are familiar from the command line interface (CLI) age, don’t translate to the GUI world without problems.

==Test Automation==

The advantages of test automation are as follows.
*Frequent regression testing
*Rapid feedback to developers - The earlier the problems are found, the cheaper it is to fix them. An automated unit test suite finds problems effectively as early as possible, long before the software reaches a customer, and even before it reaches the QA team.
*Virtually unlimited iterations of test case execution
*Support for Agile and extreme development methodologies
*Disciplined documentation of test cases
*Customized defect reporting
*Finding defects missed by manual testing

The challenge is in extending these advantages to GUI testing.

==GUI testing in Ruby and Rails==

Ruby prefers the term scripted testing over the more traditional automated testing. For testing a GUI application there can be several kind of tests in the background to verify the functionality and requirements of an application.

Various frameworks that support testing in Ruby are:
* Test:Unit - It is a unit testing framework for Ruby.
* Capybara[https://github.com/jnicklas/capybara] - It is an integration testing tool for web applications.
* Rspec[http://rspec.info/] - Behaviour Driven Development (BDD) framework/ test tool
* Cucumber[https://github.com/cucumber/cucumber] - It is a tool for running automated acceptance tests written in a behavior-driven development (BDD) style

Ruby on Rails testing frameworks are much more advanced than other web frameworks.

==GUI Testing - Pitfalls==
*Coverage criteria cannot be determined accurately with GUI testing.
*Verifying whether the GUI test executes correctly poses a problem as the logging is difficult.
*Developing a stable regression suite is difficult since simple changes in GUI can render the test suite obsolete.

==GUI Testing Tools==

GUI testing tools serve the purpose of automating the testing process of software with graphical user interfaces. Following are few of the available open source GUI testing tools:

*AutoHotkey
*CubicTest
*Dogtail
*Dojo
*Selenium
*Watir
*GNU Xnee
*Sikuli
*Webrat

==Selenium==

===Introduction===
Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language (Selenium IDE). It also provides a test domain-specific language (Selenese) to write tests in a number of popular programming languages, including Java, C#, [http://groovy.codehaus.org/ Groovy], Perl, PHP, Python and Ruby. The tests can then be run against most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.

===Selenium Tool Suite===
Selenium is composed of multiple software tools.

====Selenium IDE====
*Prototyping tool for building testscripts.
*Firefox plugin provides easy to use interface for developing automated tests.
*Supports 'record and play' feature to create reusable scripts for testing.

====Selenium1====
*Also known as Selenium RC or Remote Control
*Provides flexibility in porting tests across browsers and platforms.
*Currently in maintainence mode. No active development.

====Selenium 2====
*Also known as Selenium Webdriver
*Supports WebDriver API thus providing maximum flexibility in porting the tests.
*Runs Selenium 1’s Selenium RC interface for backwards compatibility.

====Selenium Grid====
*Selenium-Grid allows the Selenium RC solution to scale for large test suites and for test suites that must be run in multiple environments.
*Selenium Grid runs the tests in parallel, that is, different tests can be run at the same time on different remote machines.
*Selenium Grid greatly improves the time it takes to run the suite by making use of parallel processing.

===Supported Browsers and Platforms===

====Selenium 2====
*Google Chrome 12.0.712.0+
*Internet Explorer 6, 7, 8, 9 - 32 and 64-bit where applicable
*Firefox 3.0, 3.5, 3.6, 4.0, 5.0, 6, 7
*Opera 11.5+
*HtmlUnit 2.9
*Android – 2.3+ for phones and tablets (devices & emulators)
*iOS 3+ for phones (devices & emulators) and 3.2+ for tablets (devices & emulators)

====Selenium 1 and Selenium IDE====
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Browser'''
| align="center" style="background:#f0f0f0;"|'''Selenium IDE'''
| align="center" style="background:#f0f0f0;"|'''Selenium 1 (RC)'''
| align="center" style="background:#f0f0f0;"|'''Operating Systems'''
|-
| Firefox 2, 3||Record and playback tests ||Start browser, run tests||Windows, Linux, Mac
|-
| IE 6, 7, 8||Unsupported ||Start browser, run tests||Windows
|-
| Safari 2, 3, 4||Unsupported ||Start browser, run tests||Windows, Mac
|-
| Opera 8, 9, 10||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
| Google Chrome||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
|}

===Advantages===
The chief advantages of Selenium are :
*Flexibility - Test automation can be customized by adding functionality to Selenium test scripts and Selenium framework.
*Open Source - The source code can be downloaded and modified as needed to suit new browsers.
*Deploys on multiple paltforms - Windows, Linux, and Macintosh.

===Disadvantages===
*Identifying the locators and common attributes like id, names etc as well as XPATH, javascript DOM and others is difficult.
*Results are not available in good detail. Debugging failures migt prove to be difficult sometimes.
*Loop and data driven testing is not supported by Selenium IDE.
*Options to verify the images are not available.

==Auto Hot Key==
AutoHotkey automates tests by sending keystrokes and mouse clicks to the target application with the help of a macro recorder.
Virtually any key, button, or combination can become a hotkey.
Following are the notable features of hotkey:
* Expand abbreviations as you type them. For example, typing "gn" can automatically produce "good night".
* Create custom data-entry forms, user interfaces, and menu bars.
* Remap keys and buttons on your keyboard, joystick, and mouse.
* Convert any script into an EXE file that can be run on computers that don't have AutoHotkey installed.

Quick start tutorial : http://www.autohotkey.com/docs/Tutorial.htm

==Watir==
Watir, pronounced water, stands for Web Application Testing in Ruby. Watir is an open-source (BSD) family of Ruby libraries for automating web browsers. It is distributed as a Ruby GEM named 'Watir'. Watir drives browsers the same way people do. It clicks links, fills in forms, presses buttons. Watir also checks results, such as whether expected text appears on the page or not.

There are 2 version available :
* Watir-Classic : supports only Internet Explorer on Windows
* Watir-WebDriver : supports Chrome, Firefox, Internet Explorer, Opera and also running in headless mode (HTMLUnit).

==GNU Xnee==
GNU Xnee is a suite of programs that can record, replay and distribute user actions under the X11 environment. Xnee has the capability to :
* Automate tests like nightly regression
* Demonstrate programs by recording and replaying a user interaction with the system
* Distribute actions from system admin to end users.

The Record and replay ‘macro’ is the highlight of Xnee.

==DOJO==
Dojo is a JavaScript framework targeting the many needs of large-scale client-side web development.

* Dojo abstracts the differences among diverse browsers to provide APIs that will work on all of them (it can even run on the server under Node.js)
* It establishes a framework for defining modules of code and managing their inter-dependencies
* Supports internationalization, localization, and accessibility
* Provides a rich suite of commonly needed utility classes and user-interface widgets.

==CubicTest==
CubicTest is a graphical Eclipse plug-in for writing Selenium and Watir tests. It makes tests faster and easier to write, and provides abstractions to make tests more robust and reusable.

* CubicTest's test editor is centered around pages/states and transitions between these pages/states.
* The model is intuitive for both Ajax and traditional web applications and supports most user interaction types.
* CubicTest features an innovative test recorder and test runner based on Selenium RC which are fully integrated with the graphical test editor.

==Dogtail==
Dogtail is a GUI test tool and automation framework written in Python. It uses Accessibility (a11y) technologies to communicate with desktop applications. Dogtail scripts are written in Python and executed like any other Python program.
Follwoing are the notable features of Dogtail:
* Object-Oriented API: With the object oriented API, you are under control of the UI tree and its elements, allowing you to write sophisticated scripts utilizing benefits of OO right deep from dogtail.
* Procedural API: Ace programmer credentials are not necessary to write useful automated scripts with procedural API.
* Easily Extensible: Writing custom classes and helper libraries are easy.
* Results and debug reporting: Separate logs for test case comparisons and debug information are generated.

==Sikuli==
Sikuli automates GUI testing by using image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code.
* Sikuli uses an innovative approach of automating GUI tests by using screenshots and powerpoint slides.
* Sikuli Script is a visual scripting API using [http://en.wikipedia.org/wiki/Jython Jython] to create automation scripts.
* Sikuli includes an integrated development environment (IDE) for writing visual Sikuli scripts with screenshots.

==See Also==
* Web testing tools [http://en.wikipedia.org/wiki/List_of_web_testing_tools]
* Selenium Framework [http://www.mediawiki.org/wiki/Selenium_Framework]
* Selenium [http://www.jroller.com/selenium/]
* Using Selenium [http://aspyct.org/blog/2012/09/09/functional-web-testing-with-selenium-and-ruby/]
* Selenium by example [http://learnseleniumautomation.blogspot.in/2012/08/learn-selenium-webdriver-by-example.html]
* Scalable UI Testing with Selenium [http://jeffmw.com/2012/05/28/scalable-ui-testing-with-selenium/]

== Headline text ==
==References==
*http://docs.seleniumhq.org/docs/
*http://www.eecs.yorku.ca/course_archive/2004-05/W/4313/Slides/Module10-GUI.pdf - 2004-05
*http://www.cs.helsinki.fi/u/paakki/mikkolainen.pdf
*http://watir.com/
*http://www.gnu.org/software/xnee/
*https://fedorahosted.org/dogtail/
*http://www.cubictest.org/
*http://www.autohotkey.com/
*http://www.sikuli.org/
*http://sivaeluri.blogspot.com/2012/08/advantages-and-disadvantages-of.html
*http://dojotoolkit.org/reference-guide/1.9/util/dohrobot.html
*''GUI Testing: Pitfalls and Process'', Atif M. Memon, University of Maryland, IEEE Computer 2002, p. 87 - 88 [http://cvs.cs.umd.edu/~atif/papers/MemonIEEEComputer2002.pdf ]

==Note to reviewers==
The topic is very vast. Hence the wiki is written based on the guidelines provided by the TA's and the Prof.
* List all GUI tools used in OSS that you can quickly identify.
* Try to describe the tools to the same level of detail, except that you may choose to go into more detail on tools that are used with Rails.
* Listing of commands is not a good idea. You are not writing a reference manual; you are writing a descriptive article that someone might read to learn about what's available before choosing a tool or tools. You should aim for readability.

We have referred the respective tool websites to provide the overview for each one of them. We have provided appropriate citations as well. Additionally the tool and the documentation itself are under GNU/ open source licence and hence will not fall under copyright violation. Please correct us if we are wrong.

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-15T02:42:32Z

Vshesha: /* References */

[[File:Browsers.png|frame|alt=Puzzle globe|GUI Testing]]
'''Open Source GUI Testing Tools'''

Graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its designed specifications.

GUI testing is difficult mainly due to following reasons :
* Large space of possibilities. Each sequence of GUI commands can result in various states. Evaluation of all these states is essential for validation of the GUI of the given software.
*[http://en.wikipedia.org/wiki/Event-driven_architecture Event-driven architecture]. The test suite has to simulate the various user created actions.

Following are the challenges encountered while testing the graphical user interface of any software or system:
* Automation is difficult.
* The scope for testing is enormous
* Inability to determine the state of the program from GUI.
* [http://en.wikipedia.org/wiki/Regression_testing Regression testing] is difficult. Testcases may not be reusable

The current trend in user interfaces is geared towards graphical user interfaces (GUIs). This presents a problem for designing tests for software, since GUIs are very complex and hence GUI testing is very time consuming. Automation is a requirement for testing any larger graphical user interfaces, but automating GUI tests is not a straightforward task. Techniques which are familiar from the command line interface (CLI) age, don’t translate to the GUI world without problems.

==Test Automation==

The advantages of test automation are as follows.
*Frequent regression testing
*Rapid feedback to developers - The earlier the problems are found, the cheaper it is to fix them. An automated unit test suite finds problems effectively as early as possible, long before the software reaches a customer, and even before it reaches the QA team.
*Virtually unlimited iterations of test case execution
*Support for Agile and extreme development methodologies
*Disciplined documentation of test cases
*Customized defect reporting
*Finding defects missed by manual testing

The challenge is in extending these advantages to GUI testing.

==GUI testing in Ruby and Rails==

Ruby prefers the term scripted testing over the more traditional automated testing. For testing a GUI application there can be several kind of tests in the background to verify the functionality and requirements of an application.

Various frameworks that support testing in Ruby are:
* Test:Unit - It is a unit testing framework for Ruby.
* Capybara[https://github.com/jnicklas/capybara] - It is an integration testing tool for web applications.
* Rspec[http://rspec.info/] - Behaviour Driven Development (BDD) framework/ test tool
* Cucumber[https://github.com/cucumber/cucumber] - It is a tool for running automated acceptance tests written in a behavior-driven development (BDD) style

Ruby on Rails testing frameworks are much more advanced than other web frameworks.

==GUI Testing - Pitfalls==
*Coverage criteria cannot be determined accurately with GUI testing.
*Verifying whether the GUI test executes correctly poses a problem as the logging is difficult.
*Developing a stable regression suite is difficult since simple changes in GUI can render the test suite obsolete.

==GUI Testing Tools==

GUI testing tools serve the purpose of automating the testing process of software with graphical user interfaces. Following are few of the available open source GUI testing tools:

*AutoHotkey
*CubicTest
*Dogtail
*Dojo
*Selenium
*Watir
*GNU Xnee
*Sikuli
*Webrat

==Selenium==

===Introduction===
Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language (Selenium IDE). It also provides a test domain-specific language (Selenese) to write tests in a number of popular programming languages, including Java, C#, [http://groovy.codehaus.org/ Groovy], Perl, PHP, Python and Ruby. The tests can then be run against most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.

===Selenium Tool Suite===
Selenium is composed of multiple software tools.

====Selenium IDE====
*Prototyping tool for building testscripts.
*Firefox plugin provides easy to use interface for developing automated tests.
*Supports 'record and play' feature to create reusable scripts for testing.

====Selenium1====
*Also known as Selenium RC or Remote Control
*Provides flexibility in porting tests across browsers and platforms.
*Currently in maintainence mode. No active development.

====Selenium 2====
*Also known as Selenium Webdriver
*Supports WebDriver API thus providing maximum flexibility in porting the tests.
*Runs Selenium 1’s Selenium RC interface for backwards compatibility.

====Selenium Grid====
*Selenium-Grid allows the Selenium RC solution to scale for large test suites and for test suites that must be run in multiple environments.
*Selenium Grid runs the tests in parallel, that is, different tests can be run at the same time on different remote machines.
*Selenium Grid greatly improves the time it takes to run the suite by making use of parallel processing.

===Supported Browsers and Platforms===

====Selenium 2====
*Google Chrome 12.0.712.0+
*Internet Explorer 6, 7, 8, 9 - 32 and 64-bit where applicable
*Firefox 3.0, 3.5, 3.6, 4.0, 5.0, 6, 7
*Opera 11.5+
*HtmlUnit 2.9
*Android – 2.3+ for phones and tablets (devices & emulators)
*iOS 3+ for phones (devices & emulators) and 3.2+ for tablets (devices & emulators)

====Selenium 1 and Selenium IDE====
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Browser'''
| align="center" style="background:#f0f0f0;"|'''Selenium IDE'''
| align="center" style="background:#f0f0f0;"|'''Selenium 1 (RC)'''
| align="center" style="background:#f0f0f0;"|'''Operating Systems'''
|-
| Firefox 2, 3||Record and playback tests ||Start browser, run tests||Windows, Linux, Mac
|-
| IE 6, 7, 8||Unsupported ||Start browser, run tests||Windows
|-
| Safari 2, 3, 4||Unsupported ||Start browser, run tests||Windows, Mac
|-
| Opera 8, 9, 10||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
| Google Chrome||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
|}

===Advantages===
The chief advantages of Selenium are :
*Flexibility - Test automation can be customized by adding functionality to Selenium test scripts and Selenium framework.
*Open Source - The source code can be downloaded and modified as needed to suit new browsers.
*Deploys on multiple paltforms - Windows, Linux, and Macintosh.

===Disadvantages===
*Identifying the locators and common attributes like id, names etc as well as XPATH, javascript DOM and others is difficult.
*Results are not available in good detail. Debugging failures migt prove to be difficult sometimes.
*Loop and data driven testing is not supported by Selenium IDE.
*Options to verify the images are not available.

==Auto Hot Key==
AutoHotkey automates tests by sending keystrokes and mouse clicks to the target application with the help of a macro recorder.
Virtually any key, button, or combination can become a hotkey.
Following are the notable features of hotkey:
* Expand abbreviations as you type them. For example, typing "gn" can automatically produce "good night".
* Create custom data-entry forms, user interfaces, and menu bars.
* Remap keys and buttons on your keyboard, joystick, and mouse.
* Convert any script into an EXE file that can be run on computers that don't have AutoHotkey installed.

Quick start tutorial : http://www.autohotkey.com/docs/Tutorial.htm

==Watir==
Watir, pronounced water, stands for Web Application Testing in Ruby. Watir is an open-source (BSD) family of Ruby libraries for automating web browsers. It is distributed as a Ruby GEM named 'Watir'. Watir drives browsers the same way people do. It clicks links, fills in forms, presses buttons. Watir also checks results, such as whether expected text appears on the page or not.

There are 2 version available :
* Watir-Classic : supports only Internet Explorer on Windows
* Watir-WebDriver : supports Chrome, Firefox, Internet Explorer, Opera and also running in headless mode (HTMLUnit).

==GNU Xnee==
GNU Xnee is a suite of programs that can record, replay and distribute user actions under the X11 environment. Xnee has the capability to :
* Automate tests like nightly regression
* Demonstrate programs by recording and replaying a user interaction with the system
* Distribute actions from system admin to end users.

The Record and replay ‘macro’ is the highlight of Xnee.

==DOJO==
Dojo is a JavaScript framework targeting the many needs of large-scale client-side web development.

* Dojo abstracts the differences among diverse browsers to provide APIs that will work on all of them (it can even run on the server under Node.js)
* It establishes a framework for defining modules of code and managing their inter-dependencies
* Supports internationalization, localization, and accessibility
* Provides a rich suite of commonly needed utility classes and user-interface widgets.

==CubicTest==
CubicTest is a graphical Eclipse plug-in for writing Selenium and Watir tests. It makes tests faster and easier to write, and provides abstractions to make tests more robust and reusable.

* CubicTest's test editor is centered around pages/states and transitions between these pages/states.
* The model is intuitive for both Ajax and traditional web applications and supports most user interaction types.
* CubicTest features an innovative test recorder and test runner based on Selenium RC which are fully integrated with the graphical test editor.

==Dogtail==
Dogtail is a GUI test tool and automation framework written in Python. It uses Accessibility (a11y) technologies to communicate with desktop applications. Dogtail scripts are written in Python and executed like any other Python program.
Follwoing are the notable features of Dogtail:
* Object-Oriented API: With the object oriented API, you are under control of the UI tree and its elements, allowing you to write sophisticated scripts utilizing benefits of OO right deep from dogtail.
* Procedural API: Ace programmer credentials are not necessary to write useful automated scripts with procedural API.
* Easily Extensible: Writing custom classes and helper libraries are easy.
* Results and debug reporting: Separate logs for test case comparisons and debug information are generated.

==Sikuli==
Sikuli automates GUI testing by using image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code.
* Sikuli uses an innovative approach of automating GUI tests by using screenshots and powerpoint slides.
* Sikuli Script is a visual scripting API using [http://en.wikipedia.org/wiki/Jython Jython] to create automation scripts.
* Sikuli includes an integrated development environment (IDE) for writing visual Sikuli scripts with screenshots.

==See Also==
* Web testing tools [http://en.wikipedia.org/wiki/List_of_web_testing_tools]
* Selenium Framework [http://www.mediawiki.org/wiki/Selenium_Framework]
* Selenium [http://www.jroller.com/selenium/]
* Using Selenium [http://aspyct.org/blog/2012/09/09/functional-web-testing-with-selenium-and-ruby/]
* Selenium by example [http://learnseleniumautomation.blogspot.in/2012/08/learn-selenium-webdriver-by-example.html]
* Scalable UI Testing with Selenium [http://jeffmw.com/2012/05/28/scalable-ui-testing-with-selenium/]

==References==
*http://docs.seleniumhq.org/docs/
*http://www.eecs.yorku.ca/course_archive/2004-05/W/4313/Slides/Module10-GUI.pdf - 2004-05
*http://www.cs.helsinki.fi/u/paakki/mikkolainen.pdf
*http://watir.com/
*http://www.gnu.org/software/xnee/
*https://fedorahosted.org/dogtail/
*http://www.cubictest.org/
*http://www.autohotkey.com/
*http://www.sikuli.org/
*http://sivaeluri.blogspot.com/2012/08/advantages-and-disadvantages-of.html
*http://dojotoolkit.org/reference-guide/1.9/util/dohrobot.html
*http://cvs.cs.umd.edu/~atif/papers/MemonIEEEComputer2002.pdf - 2000

'''[[#nbFoot03a|^]]''' For the sun's size, see Miller, Edward. ''The Sun''. Academic Press, 2005, p. 1. For the moon's size, see Brown, Rebecca. "Size of the Moon," ''Scientific American'', 51(78):46. For the sun's heat, see Smith, John. ''The Sun's Heat''. Academic Press, 2005, p. 2.

==Note to reviewers==
The topic is very vast. Hence the wiki is written based on the guidelines provided by the TA's and the Prof.
* List all GUI tools used in OSS that you can quickly identify.
* Try to describe the tools to the same level of detail, except that you may choose to go into more detail on tools that are used with Rails.
* Listing of commands is not a good idea. You are not writing a reference manual; you are writing a descriptive article that someone might read to learn about what's available before choosing a tool or tools. You should aim for readability.

We have referred the respective tool websites to provide the overview for each one of them. We have provided appropriate citations as well. Additionally the tool and the documentation itself are under GNU/ open source licence and hence will not fall under copyright violation. Please correct us if we are wrong.

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-15T02:30:44Z

Vshesha:

[[File:Browsers.png|frame|alt=Puzzle globe|GUI Testing]]
'''Open Source GUI Testing Tools'''

Graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its designed specifications.

GUI testing is difficult mainly due to following reasons :
* Large space of possibilities. Each sequence of GUI commands can result in various states. Evaluation of all these states is essential for validation of the GUI of the given software.
*[http://en.wikipedia.org/wiki/Event-driven_architecture Event-driven architecture]. The test suite has to simulate the various user created actions.

Following are the challenges encountered while testing the graphical user interface of any software or system:
* Automation is difficult.
* The scope for testing is enormous
* Inability to determine the state of the program from GUI.
* [http://en.wikipedia.org/wiki/Regression_testing Regression testing] is difficult. Testcases may not be reusable

The current trend in user interfaces is geared towards graphical user interfaces (GUIs). This presents a problem for designing tests for software, since GUIs are very complex and hence GUI testing is very time consuming. Automation is a requirement for testing any larger graphical user interfaces, but automating GUI tests is not a straightforward task. Techniques which are familiar from the command line interface (CLI) age, don’t translate to the GUI world without problems.

==Test Automation==

The advantages of test automation are as follows.
*Frequent regression testing
*Rapid feedback to developers - The earlier the problems are found, the cheaper it is to fix them. An automated unit test suite finds problems effectively as early as possible, long before the software reaches a customer, and even before it reaches the QA team.
*Virtually unlimited iterations of test case execution
*Support for Agile and extreme development methodologies
*Disciplined documentation of test cases
*Customized defect reporting
*Finding defects missed by manual testing

The challenge is in extending these advantages to GUI testing.

==GUI testing in Ruby and Rails==

Ruby prefers the term scripted testing over the more traditional automated testing. For testing a GUI application there can be several kind of tests in the background to verify the functionality and requirements of an application.

Various frameworks that support testing in Ruby are:
* Test:Unit - It is a unit testing framework for Ruby.
* Capybara[https://github.com/jnicklas/capybara] - It is an integration testing tool for web applications.
* Rspec[http://rspec.info/] - Behaviour Driven Development (BDD) framework/ test tool
* Cucumber[https://github.com/cucumber/cucumber] - It is a tool for running automated acceptance tests written in a behavior-driven development (BDD) style

Ruby on Rails testing frameworks are much more advanced than other web frameworks.

==GUI Testing - Pitfalls==
*Coverage criteria cannot be determined accurately with GUI testing.
*Verifying whether the GUI test executes correctly poses a problem as the logging is difficult.
*Developing a stable regression suite is difficult since simple changes in GUI can render the test suite obsolete.

==GUI Testing Tools==

GUI testing tools serve the purpose of automating the testing process of software with graphical user interfaces. Following are few of the available open source GUI testing tools:

*AutoHotkey
*CubicTest
*Dogtail
*Dojo
*Selenium
*Watir
*GNU Xnee
*Sikuli

==Selenium==

===Introduction===
Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language (Selenium IDE). It also provides a test domain-specific language (Selenese) to write tests in a number of popular programming languages, including Java, C#, [http://groovy.codehaus.org/ Groovy], Perl, PHP, Python and Ruby. The tests can then be run against most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.

===Selenium Tool Suite===
Selenium is composed of multiple software tools.

====Selenium IDE====
*Prototyping tool for building testscripts.
*Firefox plugin provides easy to use interface for developing automated tests.
*Supports 'record and play' feature to create reusable scripts for testing.

====Selenium1====
*Also known as Selenium RC or Remote Control
*Provides flexibility in porting tests across browsers and platforms.
*Currently in maintainence mode. No active development.

====Selenium 2====
*Also known as Selenium Webdriver
*Supports WebDriver API thus providing maximum flexibility in porting the tests.
*Runs Selenium 1’s Selenium RC interface for backwards compatibility.

====Selenium Grid====
*Selenium-Grid allows the Selenium RC solution to scale for large test suites and for test suites that must be run in multiple environments.
*Selenium Grid runs the tests in parallel, that is, different tests can be run at the same time on different remote machines.
*Selenium Grid greatly improves the time it takes to run the suite by making use of parallel processing.

===Supported Browsers and Platforms===

====Selenium 2====
*Google Chrome 12.0.712.0+
*Internet Explorer 6, 7, 8, 9 - 32 and 64-bit where applicable
*Firefox 3.0, 3.5, 3.6, 4.0, 5.0, 6, 7
*Opera 11.5+
*HtmlUnit 2.9
*Android – 2.3+ for phones and tablets (devices & emulators)
*iOS 3+ for phones (devices & emulators) and 3.2+ for tablets (devices & emulators)

====Selenium 1 and Selenium IDE====
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Browser'''
| align="center" style="background:#f0f0f0;"|'''Selenium IDE'''
| align="center" style="background:#f0f0f0;"|'''Selenium 1 (RC)'''
| align="center" style="background:#f0f0f0;"|'''Operating Systems'''
|-
| Firefox 2, 3||Record and playback tests ||Start browser, run tests||Windows, Linux, Mac
|-
| IE 6, 7, 8||Unsupported ||Start browser, run tests||Windows
|-
| Safari 2, 3, 4||Unsupported ||Start browser, run tests||Windows, Mac
|-
| Opera 8, 9, 10||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
| Google Chrome||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
|}

===Advantages===
The chief advantages of Selenium are :
*Flexibility - Test automation can be customized by adding functionality to Selenium test scripts and Selenium framework.
*Open Source - The source code can be downloaded and modified as needed to suit new browsers.
*Deploys on multiple paltforms - Windows, Linux, and Macintosh.

===Disadvantages===
*Identifying the locators and common attributes like id, names etc as well as XPATH, javascript DOM and others is difficult.
*Results are not available in good detail. Debugging failures migt prove to be difficult sometimes.
*Loop and data driven testing is not supported by Selenium IDE.
*Options to verify the images are not available.

==Auto Hot Key==
AutoHotkey automates tests by sending keystrokes and mouse clicks to the target application with the help of a macro recorder.
Virtually any key, button, or combination can become a hotkey.
Following are the notable features of hotkey:
* Expand abbreviations as you type them. For example, typing "gn" can automatically produce "good night".
* Create custom data-entry forms, user interfaces, and menu bars.
* Remap keys and buttons on your keyboard, joystick, and mouse.
* Convert any script into an EXE file that can be run on computers that don't have AutoHotkey installed.

Quick start tutorial : http://www.autohotkey.com/docs/Tutorial.htm

==Watir==
Watir, pronounced water, stands for Web Application Testing in Ruby. Watir is an open-source (BSD) family of Ruby libraries for automating web browsers. It is distributed as a Ruby GEM named 'Watir'. Watir drives browsers the same way people do. It clicks links, fills in forms, presses buttons. Watir also checks results, such as whether expected text appears on the page or not.

There are 2 version available :
* Watir-Classic : supports only Internet Explorer on Windows
* Watir-WebDriver : supports Chrome, Firefox, Internet Explorer, Opera and also running in headless mode (HTMLUnit).

==GNU Xnee==
GNU Xnee is a suite of programs that can record, replay and distribute user actions under the X11 environment. Xnee has the capability to :
* Automate tests like nightly regression
* Demonstrate programs by recording and replaying a user interaction with the system
* Distribute actions from system admin to end users.

The Record and replay ‘macro’ is the highlight of Xnee.

==DOJO==
Dojo is a JavaScript framework targeting the many needs of large-scale client-side web development.

* Dojo abstracts the differences among diverse browsers to provide APIs that will work on all of them (it can even run on the server under Node.js)
* It establishes a framework for defining modules of code and managing their inter-dependencies
* Supports internationalization, localization, and accessibility
* Provides a rich suite of commonly needed utility classes and user-interface widgets.

==CubicTest==
CubicTest is a graphical Eclipse plug-in for writing Selenium and Watir tests. It makes tests faster and easier to write, and provides abstractions to make tests more robust and reusable.

* CubicTest's test editor is centered around pages/states and transitions between these pages/states.
* The model is intuitive for both Ajax and traditional web applications and supports most user interaction types.
* CubicTest features an innovative test recorder and test runner based on Selenium RC which are fully integrated with the graphical test editor.

==Dogtail==
Dogtail is a GUI test tool and automation framework written in Python. It uses Accessibility (a11y) technologies to communicate with desktop applications. Dogtail scripts are written in Python and executed like any other Python program.
Follwoing are the notable features of Dogtail:
* Object-Oriented API: With the object oriented API, you are under control of the UI tree and its elements, allowing you to write sophisticated scripts utilizing benefits of OO right deep from dogtail.
* Procedural API: Ace programmer credentials are not necessary to write useful automated scripts with procedural API.
* Easily Extensible: Writing custom classes and helper libraries are easy.
* Results and debug reporting: Separate logs for test case comparisons and debug information are generated.

==Sikuli==
Sikuli automates GUI testing by using image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code.
* Sikuli uses an innovative approach of automating GUI tests by using screenshots and powerpoint slides.
* Sikuli Script is a visual scripting API using [http://en.wikipedia.org/wiki/Jython Jython] to create automation scripts.
* Sikuli includes an integrated development environment (IDE) for writing visual Sikuli scripts with screenshots.

==See Also==
* Web testing tools [http://en.wikipedia.org/wiki/List_of_web_testing_tools]
* Selenium Framework [http://www.mediawiki.org/wiki/Selenium_Framework]
* Selenium [http://www.jroller.com/selenium/]
* Using Selenium [http://aspyct.org/blog/2012/09/09/functional-web-testing-with-selenium-and-ruby/]
* Selenium by example [http://learnseleniumautomation.blogspot.in/2012/08/learn-selenium-webdriver-by-example.html]
* Scalable UI Testing with Selenium [http://jeffmw.com/2012/05/28/scalable-ui-testing-with-selenium/]

==References==
*http://docs.seleniumhq.org/docs/
*http://www.eecs.yorku.ca/course_archive/2004-05/W/4313/Slides/Module10-GUI.pdf - 2004-05
*http://www.cs.helsinki.fi/u/paakki/mikkolainen.pdf
*http://watir.com/
*http://www.gnu.org/software/xnee/
*https://fedorahosted.org/dogtail/
*http://www.cubictest.org/
*http://www.autohotkey.com/
*http://www.sikuli.org/
*http://sivaeluri.blogspot.com/2012/08/advantages-and-disadvantages-of.html
*http://dojotoolkit.org/reference-guide/1.9/util/dohrobot.html
*http://cvs.cs.umd.edu/~atif/papers/MemonIEEEComputer2002.pdf - 2000

==Note to reviewers==
The topic is very vast. Hence the wiki is written based on the guidelines provided by the TA's and the Prof.
* List all GUI tools used in OSS that you can quickly identify.
* Try to describe the tools to the same level of detail, except that you may choose to go into more detail on tools that are used with Rails.
* Listing of commands is not a good idea. You are not writing a reference manual; you are writing a descriptive article that someone might read to learn about what's available before choosing a tool or tools. You should aim for readability.

We have referred the respective tool websites to provide the overview for each one of them. We have provided appropriate citations as well. Additionally the tool and the documentation itself are under GNU/ open source licence and hence will not fall under copyright violation. Please correct us if we are wrong.

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-15T02:26:55Z

Vshesha:

'''Open Source GUI Testing Tools'''
[[File:Browsers.png|frame|alt=Puzzle globe|GUI Testing]]

Graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its designed specifications.

GUI testing is difficult mainly due to following reasons :
* Large space of possibilities. Each sequence of GUI commands can result in various states. Evaluation of all these states is essential for validation of the GUI of the given software.
*[http://en.wikipedia.org/wiki/Event-driven_architecture Event-driven architecture]. The test suite has to simulate the various user created actions.

Following are the challenges encountered while testing the graphical user interface of any software or system:
* Automation is difficult.
* The scope for testing is enormous
* Inability to determine the state of the program from GUI.
* [http://en.wikipedia.org/wiki/Regression_testing Regression testing] is difficult. Testcases may not be reusable

The current trend in user interfaces is geared towards graphical user interfaces (GUIs). This presents a problem for designing tests for software, since GUIs are very complex and hence GUI testing is very time consuming. Automation is a requirement for testing any larger graphical user interfaces, but automating GUI tests is not a straightforward task. Techniques which are familiar from the command line interface (CLI) age, don’t translate to the GUI world without problems.

==Test Automation==

The advantages of test automation are as follows.
*Frequent regression testing
*Rapid feedback to developers - The earlier the problems are found, the cheaper it is to fix them. An automated unit test suite finds problems effectively as early as possible, long before the software reaches a customer, and even before it reaches the QA team.
*Virtually unlimited iterations of test case execution
*Support for Agile and extreme development methodologies
*Disciplined documentation of test cases
*Customized defect reporting
*Finding defects missed by manual testing

The challenge is in extending these advantages to GUI testing.

==GUI testing in Ruby and Rails==

Ruby prefers the term scripted testing over the more traditional automated testing. For testing a GUI application there can be several kind of tests in the background to verify the functionality and requirements of an application.

Various frameworks that support testing in Ruby are:
* Test:Unit - It is a unit testing framework for Ruby.
* Capybara[https://github.com/jnicklas/capybara] - It is an integration testing tool for web applications.
* Rspec[http://rspec.info/] - Behaviour Driven Development (BDD) framework/ test tool
* Cucumber[https://github.com/cucumber/cucumber] - It is a tool for running automated acceptance tests written in a behavior-driven development (BDD) style

Ruby on Rails testing frameworks are much more advanced than other web frameworks.

==GUI Testing - Pitfalls==
*Coverage criteria cannot be determined accurately with GUI testing.
*Verifying whether the GUI test executes correctly poses a problem as the logging is difficult.
*Developing a stable regression suite is difficult since simple changes in GUI can render the test suite obsolete.

==GUI Testing Tools==

GUI testing tools serve the purpose of automating the testing process of software with graphical user interfaces. Following are few of the available open source GUI testing tools:

*AutoHotkey
*CubicTest
*Dogtail
*Dojo
*Selenium
*Watir
*GNU Xnee
*Sikuli

==Selenium==

===Introduction===
Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language (Selenium IDE). It also provides a test domain-specific language (Selenese) to write tests in a number of popular programming languages, including Java, C#, [http://groovy.codehaus.org/ Groovy], Perl, PHP, Python and Ruby. The tests can then be run against most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.

===Selenium Tool Suite===
Selenium is composed of multiple software tools.

====Selenium IDE====
*Prototyping tool for building testscripts.
*Firefox plugin provides easy to use interface for developing automated tests.
*Supports 'record and play' feature to create reusable scripts for testing.

====Selenium1====
*Also known as Selenium RC or Remote Control
*Provides flexibility in porting tests across browsers and platforms.
*Currently in maintainence mode. No active development.

====Selenium 2====
*Also known as Selenium Webdriver
*Supports WebDriver API thus providing maximum flexibility in porting the tests.
*Runs Selenium 1’s Selenium RC interface for backwards compatibility.

====Selenium Grid====
*Selenium-Grid allows the Selenium RC solution to scale for large test suites and for test suites that must be run in multiple environments.
*Selenium Grid runs the tests in parallel, that is, different tests can be run at the same time on different remote machines.
*Selenium Grid greatly improves the time it takes to run the suite by making use of parallel processing.

===Supported Browsers and Platforms===

====Selenium 2====
*Google Chrome 12.0.712.0+
*Internet Explorer 6, 7, 8, 9 - 32 and 64-bit where applicable
*Firefox 3.0, 3.5, 3.6, 4.0, 5.0, 6, 7
*Opera 11.5+
*HtmlUnit 2.9
*Android – 2.3+ for phones and tablets (devices & emulators)
*iOS 3+ for phones (devices & emulators) and 3.2+ for tablets (devices & emulators)

====Selenium 1 and Selenium IDE====
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Browser'''
| align="center" style="background:#f0f0f0;"|'''Selenium IDE'''
| align="center" style="background:#f0f0f0;"|'''Selenium 1 (RC)'''
| align="center" style="background:#f0f0f0;"|'''Operating Systems'''
|-
| Firefox 2, 3||Record and playback tests ||Start browser, run tests||Windows, Linux, Mac
|-
| IE 6, 7, 8||Unsupported ||Start browser, run tests||Windows
|-
| Safari 2, 3, 4||Unsupported ||Start browser, run tests||Windows, Mac
|-
| Opera 8, 9, 10||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
| Google Chrome||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
|}

===Advantages===
The chief advantages of Selenium are :
*Flexibility - Test automation can be customized by adding functionality to Selenium test scripts and Selenium framework.
*Open Source - The source code can be downloaded and modified as needed to suit new browsers.
*Deploys on multiple paltforms - Windows, Linux, and Macintosh.

===Disadvantages===
*Identifying the locators and common attributes like id, names etc as well as XPATH, javascript DOM and others is difficult.
*Results are not available in good detail. Debugging failures migt prove to be difficult sometimes.
*Loop and data driven testing is not supported by Selenium IDE.
*Options to verify the images are not available.

==Auto Hot Key==
AutoHotkey automates tests by sending keystrokes and mouse clicks to the target application with the help of a macro recorder.
Virtually any key, button, or combination can become a hotkey.
Following are the notable features of hotkey:
* Expand abbreviations as you type them. For example, typing "gn" can automatically produce "good night".
* Create custom data-entry forms, user interfaces, and menu bars.
* Remap keys and buttons on your keyboard, joystick, and mouse.
* Convert any script into an EXE file that can be run on computers that don't have AutoHotkey installed.

Quick start tutorial : http://www.autohotkey.com/docs/Tutorial.htm

==Watir==
Watir, pronounced water, stands for Web Application Testing in Ruby. Watir is an open-source (BSD) family of Ruby libraries for automating web browsers. It is distributed as a Ruby GEM named 'Watir'. Watir drives browsers the same way people do. It clicks links, fills in forms, presses buttons. Watir also checks results, such as whether expected text appears on the page or not.

There are 2 version available :
* Watir-Classic : supports only Internet Explorer on Windows
* Watir-WebDriver : supports Chrome, Firefox, Internet Explorer, Opera and also running in headless mode (HTMLUnit).

==GNU Xnee==
GNU Xnee is a suite of programs that can record, replay and distribute user actions under the X11 environment. Xnee has the capability to :
* Automate tests like nightly regression
* Demonstrate programs by recording and replaying a user interaction with the system
* Distribute actions from system admin to end users.

The Record and replay ‘macro’ is the highlight of Xnee.

==DOJO==
Dojo is a JavaScript framework targeting the many needs of large-scale client-side web development.

* Dojo abstracts the differences among diverse browsers to provide APIs that will work on all of them (it can even run on the server under Node.js)
* It establishes a framework for defining modules of code and managing their inter-dependencies
* Supports internationalization, localization, and accessibility
* Provides a rich suite of commonly needed utility classes and user-interface widgets.

==CubicTest==
CubicTest is a graphical Eclipse plug-in for writing Selenium and Watir tests. It makes tests faster and easier to write, and provides abstractions to make tests more robust and reusable.

* CubicTest's test editor is centered around pages/states and transitions between these pages/states.
* The model is intuitive for both Ajax and traditional web applications and supports most user interaction types.
* CubicTest features an innovative test recorder and test runner based on Selenium RC which are fully integrated with the graphical test editor.

==Dogtail==
Dogtail is a GUI test tool and automation framework written in Python. It uses Accessibility (a11y) technologies to communicate with desktop applications. Dogtail scripts are written in Python and executed like any other Python program.
Follwoing are the notable features of Dogtail:
* Object-Oriented API: With the object oriented API, you are under control of the UI tree and its elements, allowing you to write sophisticated scripts utilizing benefits of OO right deep from dogtail.
* Procedural API: Ace programmer credentials are not necessary to write useful automated scripts with procedural API.
* Easily Extensible: Writing custom classes and helper libraries are easy.
* Results and debug reporting: Separate logs for test case comparisons and debug information are generated.

==Sikuli==
Sikuli automates GUI testing by using image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code.
* Sikuli uses an innovative approach of automating GUI tests by using screenshots and powerpoint slides.
* Sikuli Script is a visual scripting API using [http://en.wikipedia.org/wiki/Jython Jython] to create automation scripts.
* Sikuli includes an integrated development environment (IDE) for writing visual Sikuli scripts with screenshots.

==See Also==
* Web testing tools [http://en.wikipedia.org/wiki/List_of_web_testing_tools]
* Selenium Framework [http://www.mediawiki.org/wiki/Selenium_Framework]
* Selenium [http://www.jroller.com/selenium/]
* Using Selenium [http://aspyct.org/blog/2012/09/09/functional-web-testing-with-selenium-and-ruby/]
* Selenium by example [http://learnseleniumautomation.blogspot.in/2012/08/learn-selenium-webdriver-by-example.html]
* Scalable UI Testing with Selenium [http://jeffmw.com/2012/05/28/scalable-ui-testing-with-selenium/]

==References==
*http://docs.seleniumhq.org/docs/
*http://www.eecs.yorku.ca/course_archive/2004-05/W/4313/Slides/Module10-GUI.pdf - 2004-05
*http://www.cs.helsinki.fi/u/paakki/mikkolainen.pdf
*http://watir.com/
*http://www.gnu.org/software/xnee/
*https://fedorahosted.org/dogtail/
*http://www.cubictest.org/
*http://www.autohotkey.com/
*http://www.sikuli.org/
*http://sivaeluri.blogspot.com/2012/08/advantages-and-disadvantages-of.html
*http://dojotoolkit.org/reference-guide/1.9/util/dohrobot.html
*http://cvs.cs.umd.edu/~atif/papers/MemonIEEEComputer2002.pdf - 2000

==Note to reviewers==
The topic is very vast. Hence the wiki is written based on the guidelines provided by the TA's and the Prof.
* List all GUI tools used in OSS that you can quickly identify.
* Try to describe the tools to the same level of detail, except that you may choose to go into more detail on tools that are used with Rails.
* Listing of commands is not a good idea. You are not writing a reference manual; you are writing a descriptive article that someone might read to learn about what's available before choosing a tool or tools. You should aim for readability.

We have referred the respective tool websites to provide the overview for each one of them. We have provided appropriate citations as well. Additionally the tool and the documentation itself are under GNU/ open source licence and hence will not fall under copyright violation. Please correct us if we are wrong.

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-15T02:25:45Z

Vshesha:

[[File:Browsers.png|frame|alt=Puzzle globe|GUI Testing]]

Graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its designed specifications.

GUI testing is difficult mainly due to following reasons :
* Large space of possibilities. Each sequence of GUI commands can result in various states. Evaluation of all these states is essential for validation of the GUI of the given software.
*[http://en.wikipedia.org/wiki/Event-driven_architecture Event-driven architecture]. The test suite has to simulate the various user created actions.

Following are the challenges encountered while testing the graphical user interface of any software or system:
* Automation is difficult.
* The scope for testing is enormous
* Inability to determine the state of the program from GUI.
* [http://en.wikipedia.org/wiki/Regression_testing Regression testing] is difficult. Testcases may not be reusable

The current trend in user interfaces is geared towards graphical user interfaces (GUIs). This presents a problem for designing tests for software, since GUIs are very complex and hence GUI testing is very time consuming. Automation is a requirement for testing any larger graphical user interfaces, but automating GUI tests is not a straightforward task. Techniques which are familiar from the command line interface (CLI) age, don’t translate to the GUI world without problems.

==Test Automation==

The advantages of test automation are as follows.
*Frequent regression testing
*Rapid feedback to developers - The earlier the problems are found, the cheaper it is to fix them. An automated unit test suite finds problems effectively as early as possible, long before the software reaches a customer, and even before it reaches the QA team.
*Virtually unlimited iterations of test case execution
*Support for Agile and extreme development methodologies
*Disciplined documentation of test cases
*Customized defect reporting
*Finding defects missed by manual testing

The challenge is in extending these advantages to GUI testing.

==GUI testing in Ruby and Rails==

Ruby prefers the term scripted testing over the more traditional automated testing. For testing a GUI application there can be several kind of tests in the background to verify the functionality and requirements of an application.

Various frameworks that support testing in Ruby are:
* Test:Unit - It is a unit testing framework for Ruby.
* Capybara[https://github.com/jnicklas/capybara] - It is an integration testing tool for web applications.
* Rspec[http://rspec.info/] - Behaviour Driven Development (BDD) framework/ test tool
* Cucumber[https://github.com/cucumber/cucumber] - It is a tool for running automated acceptance tests written in a behavior-driven development (BDD) style

Ruby on Rails testing frameworks are much more advanced than other web frameworks.

==GUI Testing - Pitfalls==
*Coverage criteria cannot be determined accurately with GUI testing.
*Verifying whether the GUI test executes correctly poses a problem as the logging is difficult.
*Developing a stable regression suite is difficult since simple changes in GUI can render the test suite obsolete.

==GUI Testing Tools==

GUI testing tools serve the purpose of automating the testing process of software with graphical user interfaces. Following are few of the available open source GUI testing tools:

*AutoHotkey
*CubicTest
*Dogtail
*Dojo
*Selenium
*Watir
*GNU Xnee
*Sikuli

==Selenium==

===Introduction===
Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language (Selenium IDE). It also provides a test domain-specific language (Selenese) to write tests in a number of popular programming languages, including Java, C#, [http://groovy.codehaus.org/ Groovy], Perl, PHP, Python and Ruby. The tests can then be run against most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.

===Selenium Tool Suite===
Selenium is composed of multiple software tools.

====Selenium IDE====
*Prototyping tool for building testscripts.
*Firefox plugin provides easy to use interface for developing automated tests.
*Supports 'record and play' feature to create reusable scripts for testing.

====Selenium1====
*Also known as Selenium RC or Remote Control
*Provides flexibility in porting tests across browsers and platforms.
*Currently in maintainence mode. No active development.

====Selenium 2====
*Also known as Selenium Webdriver
*Supports WebDriver API thus providing maximum flexibility in porting the tests.
*Runs Selenium 1’s Selenium RC interface for backwards compatibility.

====Selenium Grid====
*Selenium-Grid allows the Selenium RC solution to scale for large test suites and for test suites that must be run in multiple environments.
*Selenium Grid runs the tests in parallel, that is, different tests can be run at the same time on different remote machines.
*Selenium Grid greatly improves the time it takes to run the suite by making use of parallel processing.

===Supported Browsers and Platforms===

====Selenium 2====
*Google Chrome 12.0.712.0+
*Internet Explorer 6, 7, 8, 9 - 32 and 64-bit where applicable
*Firefox 3.0, 3.5, 3.6, 4.0, 5.0, 6, 7
*Opera 11.5+
*HtmlUnit 2.9
*Android – 2.3+ for phones and tablets (devices & emulators)
*iOS 3+ for phones (devices & emulators) and 3.2+ for tablets (devices & emulators)

====Selenium 1 and Selenium IDE====
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Browser'''
| align="center" style="background:#f0f0f0;"|'''Selenium IDE'''
| align="center" style="background:#f0f0f0;"|'''Selenium 1 (RC)'''
| align="center" style="background:#f0f0f0;"|'''Operating Systems'''
|-
| Firefox 2, 3||Record and playback tests ||Start browser, run tests||Windows, Linux, Mac
|-
| IE 6, 7, 8||Unsupported ||Start browser, run tests||Windows
|-
| Safari 2, 3, 4||Unsupported ||Start browser, run tests||Windows, Mac
|-
| Opera 8, 9, 10||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
| Google Chrome||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
|}

===Advantages===
The chief advantages of Selenium are :
*Flexibility - Test automation can be customized by adding functionality to Selenium test scripts and Selenium framework.
*Open Source - The source code can be downloaded and modified as needed to suit new browsers.
*Deploys on multiple paltforms - Windows, Linux, and Macintosh.

===Disadvantages===
*Identifying the locators and common attributes like id, names etc as well as XPATH, javascript DOM and others is difficult.
*Results are not available in good detail. Debugging failures migt prove to be difficult sometimes.
*Loop and data driven testing is not supported by Selenium IDE.
*Options to verify the images are not available.

==Auto Hot Key==
AutoHotkey automates tests by sending keystrokes and mouse clicks to the target application with the help of a macro recorder.
Virtually any key, button, or combination can become a hotkey.
Following are the notable features of hotkey:
* Expand abbreviations as you type them. For example, typing "gn" can automatically produce "good night".
* Create custom data-entry forms, user interfaces, and menu bars.
* Remap keys and buttons on your keyboard, joystick, and mouse.
* Convert any script into an EXE file that can be run on computers that don't have AutoHotkey installed.

Quick start tutorial : http://www.autohotkey.com/docs/Tutorial.htm

==Watir==
Watir, pronounced water, stands for Web Application Testing in Ruby. Watir is an open-source (BSD) family of Ruby libraries for automating web browsers. It is distributed as a Ruby GEM named 'Watir'. Watir drives browsers the same way people do. It clicks links, fills in forms, presses buttons. Watir also checks results, such as whether expected text appears on the page or not.

There are 2 version available :
* Watir-Classic : supports only Internet Explorer on Windows
* Watir-WebDriver : supports Chrome, Firefox, Internet Explorer, Opera and also running in headless mode (HTMLUnit).

==GNU Xnee==
GNU Xnee is a suite of programs that can record, replay and distribute user actions under the X11 environment. Xnee has the capability to :
* Automate tests like nightly regression
* Demonstrate programs by recording and replaying a user interaction with the system
* Distribute actions from system admin to end users.

The Record and replay ‘macro’ is the highlight of Xnee.

==DOJO==
Dojo is a JavaScript framework targeting the many needs of large-scale client-side web development.

* Dojo abstracts the differences among diverse browsers to provide APIs that will work on all of them (it can even run on the server under Node.js)
* It establishes a framework for defining modules of code and managing their inter-dependencies
* Supports internationalization, localization, and accessibility
* Provides a rich suite of commonly needed utility classes and user-interface widgets.

==CubicTest==
CubicTest is a graphical Eclipse plug-in for writing Selenium and Watir tests. It makes tests faster and easier to write, and provides abstractions to make tests more robust and reusable.

* CubicTest's test editor is centered around pages/states and transitions between these pages/states.
* The model is intuitive for both Ajax and traditional web applications and supports most user interaction types.
* CubicTest features an innovative test recorder and test runner based on Selenium RC which are fully integrated with the graphical test editor.

==Dogtail==
Dogtail is a GUI test tool and automation framework written in Python. It uses Accessibility (a11y) technologies to communicate with desktop applications. Dogtail scripts are written in Python and executed like any other Python program.
Follwoing are the notable features of Dogtail:
* Object-Oriented API: With the object oriented API, you are under control of the UI tree and its elements, allowing you to write sophisticated scripts utilizing benefits of OO right deep from dogtail.
* Procedural API: Ace programmer credentials are not necessary to write useful automated scripts with procedural API.
* Easily Extensible: Writing custom classes and helper libraries are easy.
* Results and debug reporting: Separate logs for test case comparisons and debug information are generated.

==Sikuli==
Sikuli automates GUI testing by using image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code.
* Sikuli uses an innovative approach of automating GUI tests by using screenshots and powerpoint slides.
* Sikuli Script is a visual scripting API using [http://en.wikipedia.org/wiki/Jython Jython] to create automation scripts.
* Sikuli includes an integrated development environment (IDE) for writing visual Sikuli scripts with screenshots.

==See Also==
* Web testing tools [http://en.wikipedia.org/wiki/List_of_web_testing_tools]
* Selenium Framework [http://www.mediawiki.org/wiki/Selenium_Framework]
* Selenium [http://www.jroller.com/selenium/]
* Using Selenium [http://aspyct.org/blog/2012/09/09/functional-web-testing-with-selenium-and-ruby/]
* Selenium by example [http://learnseleniumautomation.blogspot.in/2012/08/learn-selenium-webdriver-by-example.html]
* Scalable UI Testing with Selenium [http://jeffmw.com/2012/05/28/scalable-ui-testing-with-selenium/]

==References==
*http://docs.seleniumhq.org/docs/
*http://www.eecs.yorku.ca/course_archive/2004-05/W/4313/Slides/Module10-GUI.pdf - 2004-05
*http://www.cs.helsinki.fi/u/paakki/mikkolainen.pdf
*http://watir.com/
*http://www.gnu.org/software/xnee/
*https://fedorahosted.org/dogtail/
*http://www.cubictest.org/
*http://www.autohotkey.com/
*http://www.sikuli.org/
*http://sivaeluri.blogspot.com/2012/08/advantages-and-disadvantages-of.html
*http://dojotoolkit.org/reference-guide/1.9/util/dohrobot.html
*http://cvs.cs.umd.edu/~atif/papers/MemonIEEEComputer2002.pdf - 2000

==Note to reviewers==
The topic is very vast. Hence the wiki is written based on the guidelines provided by the TA's and the Prof.
* List all GUI tools used in OSS that you can quickly identify.
* Try to describe the tools to the same level of detail, except that you may choose to go into more detail on tools that are used with Rails.
* Listing of commands is not a good idea. You are not writing a reference manual; you are writing a descriptive article that someone might read to learn about what's available before choosing a tool or tools. You should aim for readability.

We have referred the respective tool websites to provide the overview for each one of them. We have provided appropriate citations as well. Additionally the tool and the documentation itself are under GNU/ open source licence and hence will not fall under copyright violation. Please correct us if we are wrong.

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-15T02:25:10Z

Vshesha: /* GUI Testing Tools */

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-15T02:24:08Z

Vshesha: /* Open Source GUI Testing Tools */

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-15T02:23:30Z

Vshesha: /* Open Source GUI Testing Tools */

[[File:Browsers.png|frame|alt=Puzzle globe|GUI Testing]]
==Open Source GUI Testing Tools==

Graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its designed specifications.

GUI testing is difficult mainly due to following reasons :
* Large space of possibilities. Each sequence of GUI commands can result in various states. Evaluation of all these states is essential for validation of the GUI of the given software.
*[http://en.wikipedia.org/wiki/Event-driven_architecture Event-driven architecture]. The test suite has to simulate the various user created actions.

Following are the challenges encountered while testing the graphical user interface of any software or system:
* Automation is difficult.
* The scope for testing is enormous
* Inability to determine the state of the program from GUI.
* [http://en.wikipedia.org/wiki/Regression_testing Regression testing] is difficult. Testcases may not be reusable

The current trend in user interfaces is geared towards graphical user interfaces (GUIs). This presents a problem for designing tests for software, since GUIs are very complex and hence GUI testing is very time consuming. Automation is a requirement for testing any larger graphical user interfaces, but automating GUI tests is not a straightforward task. Techniques which are familiar from the command line interface (CLI) age, don’t translate to the GUI world without problems.

==Test Automation==

The advantages of test automation are as follows.
*Frequent regression testing
*Rapid feedback to developers - The earlier the problems are found, the cheaper it is to fix them. An automated unit test suite finds problems effectively as early as possible, long before the software reaches a customer, and even before it reaches the QA team.
*Virtually unlimited iterations of test case execution
*Support for Agile and extreme development methodologies
*Disciplined documentation of test cases
*Customized defect reporting
*Finding defects missed by manual testing

The challenge is in extending these advantages to GUI testing.

==GUI testing in Ruby and Rails==

Ruby prefers the term scripted testing over the more traditional automated testing. For testing a GUI application there can be several kind of tests in the background to verify the functionality and requirements of an application.

Various frameworks that support testing in Ruby are:
* Test:Unit - It is a unit testing framework for Ruby.
* Capybara[https://github.com/jnicklas/capybara] - It is an integration testing tool for web applications.
* Rspec[http://rspec.info/] - Behaviour Driven Development (BDD) framework/ test tool
* Cucumber[https://github.com/cucumber/cucumber] - It is a tool for running automated acceptance tests written in a behavior-driven development (BDD) style

Ruby on Rails testing frameworks are much more advanced than other web frameworks.

==GUI Testing - Pitfalls==
*Coverage criteria cannot be determined accurately with GUI testing.
*Verifying whether the GUI test executes correctly poses a problem as the logging is difficult.
*Developing a stable regression suite is difficult since simple changes in GUI can render the test suite obsolete.

==GUI Testing Tools==

GUI testing tools serve the purpose of automating the testing process of software with graphical user interfaces. Following are few of the available open source GUI testing tools:

*AutoHotkey
*CubicTest
*Dogtail
*Dojo
*Selenium
*Watir
*GNU Xnee
*Sikuli

==Selenium==

===Introduction===
Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language (Selenium IDE). It also provides a test domain-specific language (Selenese) to write tests in a number of popular programming languages, including Java, C#, [http://groovy.codehaus.org/ Groovy], Perl, PHP, Python and Ruby. The tests can then be run against most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.

===Selenium Tool Suite===
Selenium is composed of multiple software tools.

====Selenium IDE====
*Prototyping tool for building testscripts.
*Firefox plugin provides easy to use interface for developing automated tests.
*Supports 'record and play' feature to create reusable scripts for testing.

====Selenium1====
*Also known as Selenium RC or Remote Control
*Provides flexibility in porting tests across browsers and platforms.
*Currently in maintainence mode. No active development.

====Selenium 2====
*Also known as Selenium Webdriver
*Supports WebDriver API thus providing maximum flexibility in porting the tests.
*Runs Selenium 1’s Selenium RC interface for backwards compatibility.

====Selenium Grid====
*Selenium-Grid allows the Selenium RC solution to scale for large test suites and for test suites that must be run in multiple environments.
*Selenium Grid runs the tests in parallel, that is, different tests can be run at the same time on different remote machines.
*Selenium Grid greatly improves the time it takes to run the suite by making use of parallel processing.

===Supported Browsers and Platforms===

====Selenium 2====
*Google Chrome 12.0.712.0+
*Internet Explorer 6, 7, 8, 9 - 32 and 64-bit where applicable
*Firefox 3.0, 3.5, 3.6, 4.0, 5.0, 6, 7
*Opera 11.5+
*HtmlUnit 2.9
*Android – 2.3+ for phones and tablets (devices & emulators)
*iOS 3+ for phones (devices & emulators) and 3.2+ for tablets (devices & emulators)

====Selenium 1 and Selenium IDE====
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Browser'''
| align="center" style="background:#f0f0f0;"|'''Selenium IDE'''
| align="center" style="background:#f0f0f0;"|'''Selenium 1 (RC)'''
| align="center" style="background:#f0f0f0;"|'''Operating Systems'''
|-
| Firefox 2, 3||Record and playback tests ||Start browser, run tests||Windows, Linux, Mac
|-
| IE 6, 7, 8||Unsupported ||Start browser, run tests||Windows
|-
| Safari 2, 3, 4||Unsupported ||Start browser, run tests||Windows, Mac
|-
| Opera 8, 9, 10||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
| Google Chrome||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
|}

===Advantages===
The chief advantages of Selenium are :
*Flexibility - Test automation can be customized by adding functionality to Selenium test scripts and Selenium framework.
*Open Source - The source code can be downloaded and modified as needed to suit new browsers.
*Deploys on multiple paltforms - Windows, Linux, and Macintosh.

===Disadvantages===
*Identifying the locators and common attributes like id, names etc as well as XPATH, javascript DOM and others is difficult.
*Results are not available in good detail. Debugging failures migt prove to be difficult sometimes.
*Loop and data driven testing is not supported by Selenium IDE.
*Options to verify the images are not available.

==Auto Hot Key==
AutoHotkey automates tests by sending keystrokes and mouse clicks to the target application with the help of a macro recorder.
Virtually any key, button, or combination can become a hotkey.
Following are the notable features of hotkey:
* Expand abbreviations as you type them. For example, typing "gn" can automatically produce "good night".
* Create custom data-entry forms, user interfaces, and menu bars.
* Remap keys and buttons on your keyboard, joystick, and mouse.
* Convert any script into an EXE file that can be run on computers that don't have AutoHotkey installed.

Quick start tutorial : http://www.autohotkey.com/docs/Tutorial.htm

==Watir==
Watir, pronounced water, stands for Web Application Testing in Ruby. Watir is an open-source (BSD) family of Ruby libraries for automating web browsers. It is distributed as a Ruby GEM named 'Watir'. Watir drives browsers the same way people do. It clicks links, fills in forms, presses buttons. Watir also checks results, such as whether expected text appears on the page or not.

There are 2 version available :
* Watir-Classic : supports only Internet Explorer on Windows
* Watir-WebDriver : supports Chrome, Firefox, Internet Explorer, Opera and also running in headless mode (HTMLUnit).

==GNU Xnee==
GNU Xnee is a suite of programs that can record, replay and distribute user actions under the X11 environment. Xnee has the capability to :
* Automate tests like nightly regression
* Demonstrate programs by recording and replaying a user interaction with the system
* Distribute actions from system admin to end users.

The Record and replay ‘macro’ is the highlight of Xnee.

==DOJO==
Dojo is a JavaScript framework targeting the many needs of large-scale client-side web development.

* Dojo abstracts the differences among diverse browsers to provide APIs that will work on all of them (it can even run on the server under Node.js)
* It establishes a framework for defining modules of code and managing their inter-dependencies
* Supports internationalization, localization, and accessibility
* Provides a rich suite of commonly needed utility classes and user-interface widgets.

==CubicTest==
CubicTest is a graphical Eclipse plug-in for writing Selenium and Watir tests. It makes tests faster and easier to write, and provides abstractions to make tests more robust and reusable.

* CubicTest's test editor is centered around pages/states and transitions between these pages/states.
* The model is intuitive for both Ajax and traditional web applications and supports most user interaction types.
* CubicTest features an innovative test recorder and test runner based on Selenium RC which are fully integrated with the graphical test editor.

==Dogtail==
Dogtail is a GUI test tool and automation framework written in Python. It uses Accessibility (a11y) technologies to communicate with desktop applications. Dogtail scripts are written in Python and executed like any other Python program.
Follwoing are the notable features of Dogtail:
* Object-Oriented API: With the object oriented API, you are under control of the UI tree and its elements, allowing you to write sophisticated scripts utilizing benefits of OO right deep from dogtail.
* Procedural API: Ace programmer credentials are not necessary to write useful automated scripts with procedural API.
* Easily Extensible: Writing custom classes and helper libraries are easy.
* Results and debug reporting: Separate logs for test case comparisons and debug information are generated.

==Sikuli==
Sikuli automates GUI testing by using image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code.
* Sikuli uses an innovative approach of automating GUI tests by using screenshots and powerpoint slides.
* Sikuli Script is a visual scripting API using [http://en.wikipedia.org/wiki/Jython Jython] to create automation scripts.
* Sikuli includes an integrated development environment (IDE) for writing visual Sikuli scripts with screenshots.

==See Also==
* Web testing tools [http://en.wikipedia.org/wiki/List_of_web_testing_tools]
* Selenium Framework [http://www.mediawiki.org/wiki/Selenium_Framework]
* Selenium [http://www.jroller.com/selenium/]
* Using Selenium [http://aspyct.org/blog/2012/09/09/functional-web-testing-with-selenium-and-ruby/]
* Selenium by example [http://learnseleniumautomation.blogspot.in/2012/08/learn-selenium-webdriver-by-example.html]
* Scalable UI Testing with Selenium [http://jeffmw.com/2012/05/28/scalable-ui-testing-with-selenium/]

==References==
*http://docs.seleniumhq.org/docs/
*http://www.eecs.yorku.ca/course_archive/2004-05/W/4313/Slides/Module10-GUI.pdf - 2004-05
*http://www.cs.helsinki.fi/u/paakki/mikkolainen.pdf
*http://watir.com/
*http://www.gnu.org/software/xnee/
*https://fedorahosted.org/dogtail/
*http://www.cubictest.org/
*http://www.autohotkey.com/
*http://www.sikuli.org/
*http://sivaeluri.blogspot.com/2012/08/advantages-and-disadvantages-of.html
*http://dojotoolkit.org/reference-guide/1.9/util/dohrobot.html
*http://cvs.cs.umd.edu/~atif/papers/MemonIEEEComputer2002.pdf - 2000

==Note to reviewers==
The topic is very vast. Hence the wiki is written based on the guidelines provided by the TA's and the Prof.
* List all GUI tools used in OSS that you can quickly identify.
* Try to describe the tools to the same level of detail, except that you may choose to go into more detail on tools that are used with Rails.
* Listing of commands is not a good idea. You are not writing a reference manual; you are writing a descriptive article that someone might read to learn about what's available before choosing a tool or tools. You should aim for readability.

We have referred the respective tool websites to provide the overview for each one of them. We have provided appropriate citations as well. Additionally the tool and the documentation itself are under GNU/ open source licence and hence will not fall under copyright violation. Please correct us if we are wrong.

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-15T02:20:28Z

Vshesha: /* Open Source GUI Testing Tools */

==Open Source GUI Testing Tools==
[[File:Browsers.png|frame|alt=Puzzle globe|GUI Testing]]
Graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its designed specifications.

GUI testing is difficult mainly due to following reasons :
* Large space of possibilities. Each sequence of GUI commands can result in various states. Evaluation of all these states is essential for validation of the GUI of the given software.
*[http://en.wikipedia.org/wiki/Event-driven_architecture Event-driven architecture]. The test suite has to simulate the various user created actions.

Following are the challenges encountered while testing the graphical user interface of any software or system:
* Automation is difficult.
* The scope for testing is enormous
* Inability to determine the state of the program from GUI.
* [http://en.wikipedia.org/wiki/Regression_testing Regression testing] is difficult. Testcases may not be reusable

The current trend in user interfaces is geared towards graphical user interfaces (GUIs). This presents a problem for designing tests for software, since GUIs are very complex and hence GUI testing is very time consuming. Automation is a requirement for testing any larger graphical user interfaces, but automating GUI tests is not a straightforward task. Techniques which are familiar from the command line interface (CLI) age, don’t translate to the GUI world without problems.

==Test Automation==

The advantages of test automation are as follows.
*Frequent regression testing
*Rapid feedback to developers - The earlier the problems are found, the cheaper it is to fix them. An automated unit test suite finds problems effectively as early as possible, long before the software reaches a customer, and even before it reaches the QA team.
*Virtually unlimited iterations of test case execution
*Support for Agile and extreme development methodologies
*Disciplined documentation of test cases
*Customized defect reporting
*Finding defects missed by manual testing

The challenge is in extending these advantages to GUI testing.

==GUI testing in Ruby and Rails==

Ruby prefers the term scripted testing over the more traditional automated testing. For testing a GUI application there can be several kind of tests in the background to verify the functionality and requirements of an application.

Various frameworks that support testing in Ruby are:
* Test:Unit - It is a unit testing framework for Ruby.
* Capybara[https://github.com/jnicklas/capybara] - It is an integration testing tool for web applications.
* Rspec[http://rspec.info/] - Behaviour Driven Development (BDD) framework/ test tool
* Cucumber[https://github.com/cucumber/cucumber] - It is a tool for running automated acceptance tests written in a behavior-driven development (BDD) style

Ruby on Rails testing frameworks are much more advanced than other web frameworks.

==GUI Testing - Pitfalls==
*Coverage criteria cannot be determined accurately with GUI testing.
*Verifying whether the GUI test executes correctly poses a problem as the logging is difficult.
*Developing a stable regression suite is difficult since simple changes in GUI can render the test suite obsolete.

==GUI Testing Tools==

GUI testing tools serve the purpose of automating the testing process of software with graphical user interfaces. Following are few of the available open source GUI testing tools:

*AutoHotkey
*CubicTest
*Dogtail
*Dojo
*Selenium
*Watir
*GNU Xnee
*Sikuli

==Selenium==

===Introduction===
Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language (Selenium IDE). It also provides a test domain-specific language (Selenese) to write tests in a number of popular programming languages, including Java, C#, [http://groovy.codehaus.org/ Groovy], Perl, PHP, Python and Ruby. The tests can then be run against most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.

===Selenium Tool Suite===
Selenium is composed of multiple software tools.

====Selenium IDE====
*Prototyping tool for building testscripts.
*Firefox plugin provides easy to use interface for developing automated tests.
*Supports 'record and play' feature to create reusable scripts for testing.

====Selenium1====
*Also known as Selenium RC or Remote Control
*Provides flexibility in porting tests across browsers and platforms.
*Currently in maintainence mode. No active development.

====Selenium 2====
*Also known as Selenium Webdriver
*Supports WebDriver API thus providing maximum flexibility in porting the tests.
*Runs Selenium 1’s Selenium RC interface for backwards compatibility.

====Selenium Grid====
*Selenium-Grid allows the Selenium RC solution to scale for large test suites and for test suites that must be run in multiple environments.
*Selenium Grid runs the tests in parallel, that is, different tests can be run at the same time on different remote machines.
*Selenium Grid greatly improves the time it takes to run the suite by making use of parallel processing.

===Supported Browsers and Platforms===

====Selenium 2====
*Google Chrome 12.0.712.0+
*Internet Explorer 6, 7, 8, 9 - 32 and 64-bit where applicable
*Firefox 3.0, 3.5, 3.6, 4.0, 5.0, 6, 7
*Opera 11.5+
*HtmlUnit 2.9
*Android – 2.3+ for phones and tablets (devices & emulators)
*iOS 3+ for phones (devices & emulators) and 3.2+ for tablets (devices & emulators)

====Selenium 1 and Selenium IDE====
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Browser'''
| align="center" style="background:#f0f0f0;"|'''Selenium IDE'''
| align="center" style="background:#f0f0f0;"|'''Selenium 1 (RC)'''
| align="center" style="background:#f0f0f0;"|'''Operating Systems'''
|-
| Firefox 2, 3||Record and playback tests ||Start browser, run tests||Windows, Linux, Mac
|-
| IE 6, 7, 8||Unsupported ||Start browser, run tests||Windows
|-
| Safari 2, 3, 4||Unsupported ||Start browser, run tests||Windows, Mac
|-
| Opera 8, 9, 10||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
| Google Chrome||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
|}

===Advantages===
The chief advantages of Selenium are :
*Flexibility - Test automation can be customized by adding functionality to Selenium test scripts and Selenium framework.
*Open Source - The source code can be downloaded and modified as needed to suit new browsers.
*Deploys on multiple paltforms - Windows, Linux, and Macintosh.

===Disadvantages===
*Identifying the locators and common attributes like id, names etc as well as XPATH, javascript DOM and others is difficult.
*Results are not available in good detail. Debugging failures migt prove to be difficult sometimes.
*Loop and data driven testing is not supported by Selenium IDE.
*Options to verify the images are not available.

==Auto Hot Key==
AutoHotkey automates tests by sending keystrokes and mouse clicks to the target application with the help of a macro recorder.
Virtually any key, button, or combination can become a hotkey.
Following are the notable features of hotkey:
* Expand abbreviations as you type them. For example, typing "gn" can automatically produce "good night".
* Create custom data-entry forms, user interfaces, and menu bars.
* Remap keys and buttons on your keyboard, joystick, and mouse.
* Convert any script into an EXE file that can be run on computers that don't have AutoHotkey installed.

Quick start tutorial : http://www.autohotkey.com/docs/Tutorial.htm

==Watir==
Watir, pronounced water, stands for Web Application Testing in Ruby. Watir is an open-source (BSD) family of Ruby libraries for automating web browsers. It is distributed as a Ruby GEM named 'Watir'. Watir drives browsers the same way people do. It clicks links, fills in forms, presses buttons. Watir also checks results, such as whether expected text appears on the page or not.

There are 2 version available :
* Watir-Classic : supports only Internet Explorer on Windows
* Watir-WebDriver : supports Chrome, Firefox, Internet Explorer, Opera and also running in headless mode (HTMLUnit).

==GNU Xnee==
GNU Xnee is a suite of programs that can record, replay and distribute user actions under the X11 environment. Xnee has the capability to :
* Automate tests like nightly regression
* Demonstrate programs by recording and replaying a user interaction with the system
* Distribute actions from system admin to end users.

The Record and replay ‘macro’ is the highlight of Xnee.

==DOJO==
Dojo is a JavaScript framework targeting the many needs of large-scale client-side web development.

* Dojo abstracts the differences among diverse browsers to provide APIs that will work on all of them (it can even run on the server under Node.js)
* It establishes a framework for defining modules of code and managing their inter-dependencies
* Supports internationalization, localization, and accessibility
* Provides a rich suite of commonly needed utility classes and user-interface widgets.

==CubicTest==
CubicTest is a graphical Eclipse plug-in for writing Selenium and Watir tests. It makes tests faster and easier to write, and provides abstractions to make tests more robust and reusable.

* CubicTest's test editor is centered around pages/states and transitions between these pages/states.
* The model is intuitive for both Ajax and traditional web applications and supports most user interaction types.
* CubicTest features an innovative test recorder and test runner based on Selenium RC which are fully integrated with the graphical test editor.

==Dogtail==
Dogtail is a GUI test tool and automation framework written in Python. It uses Accessibility (a11y) technologies to communicate with desktop applications. Dogtail scripts are written in Python and executed like any other Python program.
Follwoing are the notable features of Dogtail:
* Object-Oriented API: With the object oriented API, you are under control of the UI tree and its elements, allowing you to write sophisticated scripts utilizing benefits of OO right deep from dogtail.
* Procedural API: Ace programmer credentials are not necessary to write useful automated scripts with procedural API.
* Easily Extensible: Writing custom classes and helper libraries are easy.
* Results and debug reporting: Separate logs for test case comparisons and debug information are generated.

==Sikuli==
Sikuli automates GUI testing by using image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code.
* Sikuli uses an innovative approach of automating GUI tests by using screenshots and powerpoint slides.
* Sikuli Script is a visual scripting API using [http://en.wikipedia.org/wiki/Jython Jython] to create automation scripts.
* Sikuli includes an integrated development environment (IDE) for writing visual Sikuli scripts with screenshots.

==See Also==
* Web testing tools [http://en.wikipedia.org/wiki/List_of_web_testing_tools]
* Selenium Framework [http://www.mediawiki.org/wiki/Selenium_Framework]
* Selenium [http://www.jroller.com/selenium/]
* Using Selenium [http://aspyct.org/blog/2012/09/09/functional-web-testing-with-selenium-and-ruby/]
* Selenium by example [http://learnseleniumautomation.blogspot.in/2012/08/learn-selenium-webdriver-by-example.html]
* Scalable UI Testing with Selenium [http://jeffmw.com/2012/05/28/scalable-ui-testing-with-selenium/]

==References==
*http://docs.seleniumhq.org/docs/
*http://www.eecs.yorku.ca/course_archive/2004-05/W/4313/Slides/Module10-GUI.pdf - 2004-05
*http://www.cs.helsinki.fi/u/paakki/mikkolainen.pdf
*http://watir.com/
*http://www.gnu.org/software/xnee/
*https://fedorahosted.org/dogtail/
*http://www.cubictest.org/
*http://www.autohotkey.com/
*http://www.sikuli.org/
*http://sivaeluri.blogspot.com/2012/08/advantages-and-disadvantages-of.html
*http://dojotoolkit.org/reference-guide/1.9/util/dohrobot.html
*http://cvs.cs.umd.edu/~atif/papers/MemonIEEEComputer2002.pdf - 2000

==Note to reviewers==
The topic is very vast. Hence the wiki is written based on the guidelines provided by the TA's and the Prof.
* List all GUI tools used in OSS that you can quickly identify.
* Try to describe the tools to the same level of detail, except that you may choose to go into more detail on tools that are used with Rails.
* Listing of commands is not a good idea. You are not writing a reference manual; you are writing a descriptive article that someone might read to learn about what's available before choosing a tool or tools. You should aim for readability.

We have referred the respective tool websites to provide the overview for each one of them. We have provided appropriate citations as well. Additionally the tool and the documentation itself are under GNU/ open source licence and hence will not fall under copyright violation. Please correct us if we are wrong.

File:Browsers.png

2013-10-15T02:18:56Z

Vshesha:

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-15T02:14:51Z

Vshesha: /* See Also */

==Open Source GUI Testing Tools==
Graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its designed specifications.

GUI testing is difficult mainly due to following reasons :
* Large space of possibilities. Each sequence of GUI commands can result in various states. Evaluation of all these states is essential for validation of the GUI of the given software.
*[http://en.wikipedia.org/wiki/Event-driven_architecture Event-driven architecture]. The test suite has to simulate the various user created actions.

Following are the challenges encountered while testing the graphical user interface of any software or system:
* Automation is difficult.
* The scope for testing is enormous
* Inability to determine the state of the program from GUI.
* [http://en.wikipedia.org/wiki/Regression_testing Regression testing] is difficult. Testcases may not be reusable

The current trend in user interfaces is geared towards graphical user interfaces (GUIs). This presents a problem for designing tests for software, since GUIs are very complex and hence GUI testing is very time consuming. Automation is a requirement for testing any larger graphical user interfaces, but automating GUI tests is not a straightforward task. Techniques which are familiar from the command line interface (CLI) age, don’t translate to the GUI world without problems.

==Test Automation==

The advantages of test automation are as follows.
*Frequent regression testing
*Rapid feedback to developers - The earlier the problems are found, the cheaper it is to fix them. An automated unit test suite finds problems effectively as early as possible, long before the software reaches a customer, and even before it reaches the QA team.
*Virtually unlimited iterations of test case execution
*Support for Agile and extreme development methodologies
*Disciplined documentation of test cases
*Customized defect reporting
*Finding defects missed by manual testing

The challenge is in extending these advantages to GUI testing.

==GUI testing in Ruby and Rails==

Ruby prefers the term scripted testing over the more traditional automated testing. For testing a GUI application there can be several kind of tests in the background to verify the functionality and requirements of an application.

Various frameworks that support testing in Ruby are:
* Test:Unit - It is a unit testing framework for Ruby.
* Capybara[https://github.com/jnicklas/capybara] - It is an integration testing tool for web applications.
* Rspec[http://rspec.info/] - Behaviour Driven Development (BDD) framework/ test tool
* Cucumber[https://github.com/cucumber/cucumber] - It is a tool for running automated acceptance tests written in a behavior-driven development (BDD) style

Ruby on Rails testing frameworks are much more advanced than other web frameworks.

==GUI Testing - Pitfalls==
*Coverage criteria cannot be determined accurately with GUI testing.
*Verifying whether the GUI test executes correctly poses a problem as the logging is difficult.
*Developing a stable regression suite is difficult since simple changes in GUI can render the test suite obsolete.

==GUI Testing Tools==

GUI testing tools serve the purpose of automating the testing process of software with graphical user interfaces. Following are few of the available open source GUI testing tools:

*AutoHotkey
*CubicTest
*Dogtail
*Dojo
*Selenium
*Watir
*GNU Xnee
*Sikuli

==Selenium==

===Introduction===
Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language (Selenium IDE). It also provides a test domain-specific language (Selenese) to write tests in a number of popular programming languages, including Java, C#, [http://groovy.codehaus.org/ Groovy], Perl, PHP, Python and Ruby. The tests can then be run against most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.

===Selenium Tool Suite===
Selenium is composed of multiple software tools.

====Selenium IDE====
*Prototyping tool for building testscripts.
*Firefox plugin provides easy to use interface for developing automated tests.
*Supports 'record and play' feature to create reusable scripts for testing.

====Selenium1====
*Also known as Selenium RC or Remote Control
*Provides flexibility in porting tests across browsers and platforms.
*Currently in maintainence mode. No active development.

====Selenium 2====
*Also known as Selenium Webdriver
*Supports WebDriver API thus providing maximum flexibility in porting the tests.
*Runs Selenium 1’s Selenium RC interface for backwards compatibility.

====Selenium Grid====
*Selenium-Grid allows the Selenium RC solution to scale for large test suites and for test suites that must be run in multiple environments.
*Selenium Grid runs the tests in parallel, that is, different tests can be run at the same time on different remote machines.
*Selenium Grid greatly improves the time it takes to run the suite by making use of parallel processing.

===Supported Browsers and Platforms===

====Selenium 2====
*Google Chrome 12.0.712.0+
*Internet Explorer 6, 7, 8, 9 - 32 and 64-bit where applicable
*Firefox 3.0, 3.5, 3.6, 4.0, 5.0, 6, 7
*Opera 11.5+
*HtmlUnit 2.9
*Android – 2.3+ for phones and tablets (devices & emulators)
*iOS 3+ for phones (devices & emulators) and 3.2+ for tablets (devices & emulators)

====Selenium 1 and Selenium IDE====
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Browser'''
| align="center" style="background:#f0f0f0;"|'''Selenium IDE'''
| align="center" style="background:#f0f0f0;"|'''Selenium 1 (RC)'''
| align="center" style="background:#f0f0f0;"|'''Operating Systems'''
|-
| Firefox 2, 3||Record and playback tests ||Start browser, run tests||Windows, Linux, Mac
|-
| IE 6, 7, 8||Unsupported ||Start browser, run tests||Windows
|-
| Safari 2, 3, 4||Unsupported ||Start browser, run tests||Windows, Mac
|-
| Opera 8, 9, 10||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
| Google Chrome||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
|}

===Advantages===
The chief advantages of Selenium are :
*Flexibility - Test automation can be customized by adding functionality to Selenium test scripts and Selenium framework.
*Open Source - The source code can be downloaded and modified as needed to suit new browsers.
*Deploys on multiple paltforms - Windows, Linux, and Macintosh.

===Disadvantages===
*Identifying the locators and common attributes like id, names etc as well as XPATH, javascript DOM and others is difficult.
*Results are not available in good detail. Debugging failures migt prove to be difficult sometimes.
*Loop and data driven testing is not supported by Selenium IDE.
*Options to verify the images are not available.

==Auto Hot Key==
AutoHotkey automates tests by sending keystrokes and mouse clicks to the target application with the help of a macro recorder.
Virtually any key, button, or combination can become a hotkey.
Following are the notable features of hotkey:
* Expand abbreviations as you type them. For example, typing "gn" can automatically produce "good night".
* Create custom data-entry forms, user interfaces, and menu bars.
* Remap keys and buttons on your keyboard, joystick, and mouse.
* Convert any script into an EXE file that can be run on computers that don't have AutoHotkey installed.

Quick start tutorial : http://www.autohotkey.com/docs/Tutorial.htm

==Watir==
Watir, pronounced water, stands for Web Application Testing in Ruby. Watir is an open-source (BSD) family of Ruby libraries for automating web browsers. It is distributed as a Ruby GEM named 'Watir'. Watir drives browsers the same way people do. It clicks links, fills in forms, presses buttons. Watir also checks results, such as whether expected text appears on the page or not.

There are 2 version available :
* Watir-Classic : supports only Internet Explorer on Windows
* Watir-WebDriver : supports Chrome, Firefox, Internet Explorer, Opera and also running in headless mode (HTMLUnit).

==GNU Xnee==
GNU Xnee is a suite of programs that can record, replay and distribute user actions under the X11 environment. Xnee has the capability to :
* Automate tests like nightly regression
* Demonstrate programs by recording and replaying a user interaction with the system
* Distribute actions from system admin to end users.

The Record and replay ‘macro’ is the highlight of Xnee.

==DOJO==
Dojo is a JavaScript framework targeting the many needs of large-scale client-side web development.

* Dojo abstracts the differences among diverse browsers to provide APIs that will work on all of them (it can even run on the server under Node.js)
* It establishes a framework for defining modules of code and managing their inter-dependencies
* Supports internationalization, localization, and accessibility
* Provides a rich suite of commonly needed utility classes and user-interface widgets.

==CubicTest==
CubicTest is a graphical Eclipse plug-in for writing Selenium and Watir tests. It makes tests faster and easier to write, and provides abstractions to make tests more robust and reusable.

* CubicTest's test editor is centered around pages/states and transitions between these pages/states.
* The model is intuitive for both Ajax and traditional web applications and supports most user interaction types.
* CubicTest features an innovative test recorder and test runner based on Selenium RC which are fully integrated with the graphical test editor.

==Dogtail==
Dogtail is a GUI test tool and automation framework written in Python. It uses Accessibility (a11y) technologies to communicate with desktop applications. Dogtail scripts are written in Python and executed like any other Python program.
Follwoing are the notable features of Dogtail:
* Object-Oriented API: With the object oriented API, you are under control of the UI tree and its elements, allowing you to write sophisticated scripts utilizing benefits of OO right deep from dogtail.
* Procedural API: Ace programmer credentials are not necessary to write useful automated scripts with procedural API.
* Easily Extensible: Writing custom classes and helper libraries are easy.
* Results and debug reporting: Separate logs for test case comparisons and debug information are generated.

==Sikuli==
Sikuli automates GUI testing by using image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code.
* Sikuli uses an innovative approach of automating GUI tests by using screenshots and powerpoint slides.
* Sikuli Script is a visual scripting API using [http://en.wikipedia.org/wiki/Jython Jython] to create automation scripts.
* Sikuli includes an integrated development environment (IDE) for writing visual Sikuli scripts with screenshots.

==See Also==
* Web testing tools [http://en.wikipedia.org/wiki/List_of_web_testing_tools]
* Selenium Framework [http://www.mediawiki.org/wiki/Selenium_Framework]
* Selenium [http://www.jroller.com/selenium/]
* Using Selenium [http://aspyct.org/blog/2012/09/09/functional-web-testing-with-selenium-and-ruby/]
* Selenium by example [http://learnseleniumautomation.blogspot.in/2012/08/learn-selenium-webdriver-by-example.html]
* Scalable UI Testing with Selenium [http://jeffmw.com/2012/05/28/scalable-ui-testing-with-selenium/]

==References==
*http://docs.seleniumhq.org/docs/
*http://www.eecs.yorku.ca/course_archive/2004-05/W/4313/Slides/Module10-GUI.pdf - 2004-05
*http://www.cs.helsinki.fi/u/paakki/mikkolainen.pdf
*http://watir.com/
*http://www.gnu.org/software/xnee/
*https://fedorahosted.org/dogtail/
*http://www.cubictest.org/
*http://www.autohotkey.com/
*http://www.sikuli.org/
*http://sivaeluri.blogspot.com/2012/08/advantages-and-disadvantages-of.html
*http://dojotoolkit.org/reference-guide/1.9/util/dohrobot.html
*http://cvs.cs.umd.edu/~atif/papers/MemonIEEEComputer2002.pdf - 2000

==Note to reviewers==
The topic is very vast. Hence the wiki is written based on the guidelines provided by the TA's and the Prof.
* List all GUI tools used in OSS that you can quickly identify.
* Try to describe the tools to the same level of detail, except that you may choose to go into more detail on tools that are used with Rails.
* Listing of commands is not a good idea. You are not writing a reference manual; you are writing a descriptive article that someone might read to learn about what's available before choosing a tool or tools. You should aim for readability.

We have referred the respective tool websites to provide the overview for each one of them. We have provided appropriate citations as well. Additionally the tool and the documentation itself are under GNU/ open source licence and hence will not fall under copyright violation. Please correct us if we are wrong.

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-15T02:11:46Z

Vshesha: /* OPEN SOURCE GUI TESTING TOOLS */

==Open Source GUI Testing Tools==
Graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its designed specifications.

GUI testing is difficult mainly due to following reasons :
* Large space of possibilities. Each sequence of GUI commands can result in various states. Evaluation of all these states is essential for validation of the GUI of the given software.
*[http://en.wikipedia.org/wiki/Event-driven_architecture Event-driven architecture]. The test suite has to simulate the various user created actions.

Following are the challenges encountered while testing the graphical user interface of any software or system:
* Automation is difficult.
* The scope for testing is enormous
* Inability to determine the state of the program from GUI.
* [http://en.wikipedia.org/wiki/Regression_testing Regression testing] is difficult. Testcases may not be reusable

The current trend in user interfaces is geared towards graphical user interfaces (GUIs). This presents a problem for designing tests for software, since GUIs are very complex and hence GUI testing is very time consuming. Automation is a requirement for testing any larger graphical user interfaces, but automating GUI tests is not a straightforward task. Techniques which are familiar from the command line interface (CLI) age, don’t translate to the GUI world without problems.

==Test Automation==

The advantages of test automation are as follows.
*Frequent regression testing
*Rapid feedback to developers - The earlier the problems are found, the cheaper it is to fix them. An automated unit test suite finds problems effectively as early as possible, long before the software reaches a customer, and even before it reaches the QA team.
*Virtually unlimited iterations of test case execution
*Support for Agile and extreme development methodologies
*Disciplined documentation of test cases
*Customized defect reporting
*Finding defects missed by manual testing

The challenge is in extending these advantages to GUI testing.

==GUI testing in Ruby and Rails==

Ruby prefers the term scripted testing over the more traditional automated testing. For testing a GUI application there can be several kind of tests in the background to verify the functionality and requirements of an application.

Various frameworks that support testing in Ruby are:
* Test:Unit - It is a unit testing framework for Ruby.
* Capybara[https://github.com/jnicklas/capybara] - It is an integration testing tool for web applications.
* Rspec[http://rspec.info/] - Behaviour Driven Development (BDD) framework/ test tool
* Cucumber[https://github.com/cucumber/cucumber] - It is a tool for running automated acceptance tests written in a behavior-driven development (BDD) style

Ruby on Rails testing frameworks are much more advanced than other web frameworks.

==GUI Testing - Pitfalls==
*Coverage criteria cannot be determined accurately with GUI testing.
*Verifying whether the GUI test executes correctly poses a problem as the logging is difficult.
*Developing a stable regression suite is difficult since simple changes in GUI can render the test suite obsolete.

==GUI Testing Tools==

GUI testing tools serve the purpose of automating the testing process of software with graphical user interfaces. Following are few of the available open source GUI testing tools:

*AutoHotkey
*CubicTest
*Dogtail
*Dojo
*Selenium
*Watir
*GNU Xnee
*Sikuli

==Selenium==

===Introduction===
Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language (Selenium IDE). It also provides a test domain-specific language (Selenese) to write tests in a number of popular programming languages, including Java, C#, [http://groovy.codehaus.org/ Groovy], Perl, PHP, Python and Ruby. The tests can then be run against most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.

===Selenium Tool Suite===
Selenium is composed of multiple software tools.

====Selenium IDE====
*Prototyping tool for building testscripts.
*Firefox plugin provides easy to use interface for developing automated tests.
*Supports 'record and play' feature to create reusable scripts for testing.

====Selenium1====
*Also known as Selenium RC or Remote Control
*Provides flexibility in porting tests across browsers and platforms.
*Currently in maintainence mode. No active development.

====Selenium 2====
*Also known as Selenium Webdriver
*Supports WebDriver API thus providing maximum flexibility in porting the tests.
*Runs Selenium 1’s Selenium RC interface for backwards compatibility.

====Selenium Grid====
*Selenium-Grid allows the Selenium RC solution to scale for large test suites and for test suites that must be run in multiple environments.
*Selenium Grid runs the tests in parallel, that is, different tests can be run at the same time on different remote machines.
*Selenium Grid greatly improves the time it takes to run the suite by making use of parallel processing.

===Supported Browsers and Platforms===

====Selenium 2====
*Google Chrome 12.0.712.0+
*Internet Explorer 6, 7, 8, 9 - 32 and 64-bit where applicable
*Firefox 3.0, 3.5, 3.6, 4.0, 5.0, 6, 7
*Opera 11.5+
*HtmlUnit 2.9
*Android – 2.3+ for phones and tablets (devices & emulators)
*iOS 3+ for phones (devices & emulators) and 3.2+ for tablets (devices & emulators)

====Selenium 1 and Selenium IDE====
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Browser'''
| align="center" style="background:#f0f0f0;"|'''Selenium IDE'''
| align="center" style="background:#f0f0f0;"|'''Selenium 1 (RC)'''
| align="center" style="background:#f0f0f0;"|'''Operating Systems'''
|-
| Firefox 2, 3||Record and playback tests ||Start browser, run tests||Windows, Linux, Mac
|-
| IE 6, 7, 8||Unsupported ||Start browser, run tests||Windows
|-
| Safari 2, 3, 4||Unsupported ||Start browser, run tests||Windows, Mac
|-
| Opera 8, 9, 10||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
| Google Chrome||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
|}

===Advantages===
The chief advantages of Selenium are :
*Flexibility - Test automation can be customized by adding functionality to Selenium test scripts and Selenium framework.
*Open Source - The source code can be downloaded and modified as needed to suit new browsers.
*Deploys on multiple paltforms - Windows, Linux, and Macintosh.

===Disadvantages===
*Identifying the locators and common attributes like id, names etc as well as XPATH, javascript DOM and others is difficult.
*Results are not available in good detail. Debugging failures migt prove to be difficult sometimes.
*Loop and data driven testing is not supported by Selenium IDE.
*Options to verify the images are not available.

==Auto Hot Key==
AutoHotkey automates tests by sending keystrokes and mouse clicks to the target application with the help of a macro recorder.
Virtually any key, button, or combination can become a hotkey.
Following are the notable features of hotkey:
* Expand abbreviations as you type them. For example, typing "gn" can automatically produce "good night".
* Create custom data-entry forms, user interfaces, and menu bars.
* Remap keys and buttons on your keyboard, joystick, and mouse.
* Convert any script into an EXE file that can be run on computers that don't have AutoHotkey installed.

Quick start tutorial : http://www.autohotkey.com/docs/Tutorial.htm

==Watir==
Watir, pronounced water, stands for Web Application Testing in Ruby. Watir is an open-source (BSD) family of Ruby libraries for automating web browsers. It is distributed as a Ruby GEM named 'Watir'. Watir drives browsers the same way people do. It clicks links, fills in forms, presses buttons. Watir also checks results, such as whether expected text appears on the page or not.

There are 2 version available :
* Watir-Classic : supports only Internet Explorer on Windows
* Watir-WebDriver : supports Chrome, Firefox, Internet Explorer, Opera and also running in headless mode (HTMLUnit).

==GNU Xnee==
GNU Xnee is a suite of programs that can record, replay and distribute user actions under the X11 environment. Xnee has the capability to :
* Automate tests like nightly regression
* Demonstrate programs by recording and replaying a user interaction with the system
* Distribute actions from system admin to end users.

The Record and replay ‘macro’ is the highlight of Xnee.

==DOJO==
Dojo is a JavaScript framework targeting the many needs of large-scale client-side web development.

* Dojo abstracts the differences among diverse browsers to provide APIs that will work on all of them (it can even run on the server under Node.js)
* It establishes a framework for defining modules of code and managing their inter-dependencies
* Supports internationalization, localization, and accessibility
* Provides a rich suite of commonly needed utility classes and user-interface widgets.

==CubicTest==
CubicTest is a graphical Eclipse plug-in for writing Selenium and Watir tests. It makes tests faster and easier to write, and provides abstractions to make tests more robust and reusable.

* CubicTest's test editor is centered around pages/states and transitions between these pages/states.
* The model is intuitive for both Ajax and traditional web applications and supports most user interaction types.
* CubicTest features an innovative test recorder and test runner based on Selenium RC which are fully integrated with the graphical test editor.

==Dogtail==
Dogtail is a GUI test tool and automation framework written in Python. It uses Accessibility (a11y) technologies to communicate with desktop applications. Dogtail scripts are written in Python and executed like any other Python program.
Follwoing are the notable features of Dogtail:
* Object-Oriented API: With the object oriented API, you are under control of the UI tree and its elements, allowing you to write sophisticated scripts utilizing benefits of OO right deep from dogtail.
* Procedural API: Ace programmer credentials are not necessary to write useful automated scripts with procedural API.
* Easily Extensible: Writing custom classes and helper libraries are easy.
* Results and debug reporting: Separate logs for test case comparisons and debug information are generated.

==Sikuli==
Sikuli automates GUI testing by using image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code.
* Sikuli uses an innovative approach of automating GUI tests by using screenshots and powerpoint slides.
* Sikuli Script is a visual scripting API using [http://en.wikipedia.org/wiki/Jython Jython] to create automation scripts.
* Sikuli includes an integrated development environment (IDE) for writing visual Sikuli scripts with screenshots.

==See Also==
* Web testing tools [http://en.wikipedia.org/wiki/List_of_web_testing_tools]
* Selenium Framework [http://www.mediawiki.org/wiki/Selenium_Framework]
* Selenium [http://www.jroller.com/selenium/]
* Using Selenium [http://aspyct.org/blog/2012/09/09/functional-web-testing-with-selenium-and-ruby/]
* Selenium by example [http://learnseleniumautomation.blogspot.in/2012/08/learn-selenium-webdriver-by-example.html]

==References==
*http://docs.seleniumhq.org/docs/
*http://www.eecs.yorku.ca/course_archive/2004-05/W/4313/Slides/Module10-GUI.pdf - 2004-05
*http://www.cs.helsinki.fi/u/paakki/mikkolainen.pdf
*http://watir.com/
*http://www.gnu.org/software/xnee/
*https://fedorahosted.org/dogtail/
*http://www.cubictest.org/
*http://www.autohotkey.com/
*http://www.sikuli.org/
*http://sivaeluri.blogspot.com/2012/08/advantages-and-disadvantages-of.html
*http://dojotoolkit.org/reference-guide/1.9/util/dohrobot.html
*http://cvs.cs.umd.edu/~atif/papers/MemonIEEEComputer2002.pdf - 2000

==Note to reviewers==
The topic is very vast. Hence the wiki is written based on the guidelines provided by the TA's and the Prof.
* List all GUI tools used in OSS that you can quickly identify.
* Try to describe the tools to the same level of detail, except that you may choose to go into more detail on tools that are used with Rails.
* Listing of commands is not a good idea. You are not writing a reference manual; you are writing a descriptive article that someone might read to learn about what's available before choosing a tool or tools. You should aim for readability.

We have referred the respective tool websites to provide the overview for each one of them. We have provided appropriate citations as well. Additionally the tool and the documentation itself are under GNU/ open source licence and hence will not fall under copyright violation. Please correct us if we are wrong.

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-15T02:11:13Z

Vshesha:

=='''OPEN SOURCE GUI TESTING TOOLS'''==
Graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its designed specifications.

GUI testing is difficult mainly due to following reasons :
* Large space of possibilities. Each sequence of GUI commands can result in various states. Evaluation of all these states is essential for validation of the GUI of the given software.
*[http://en.wikipedia.org/wiki/Event-driven_architecture Event-driven architecture]. The test suite has to simulate the various user created actions.

Following are the challenges encountered while testing the graphical user interface of any software or system:
* Automation is difficult.
* The scope for testing is enormous
* Inability to determine the state of the program from GUI.
* [http://en.wikipedia.org/wiki/Regression_testing Regression testing] is difficult. Testcases may not be reusable

The current trend in user interfaces is geared towards graphical user interfaces (GUIs). This presents a problem for designing tests for software, since GUIs are very complex and hence GUI testing is very time consuming. Automation is a requirement for testing any larger graphical user interfaces, but automating GUI tests is not a straightforward task. Techniques which are familiar from the command line interface (CLI) age, don’t translate to the GUI world without problems.

==Test Automation==

The advantages of test automation are as follows.
*Frequent regression testing
*Rapid feedback to developers - The earlier the problems are found, the cheaper it is to fix them. An automated unit test suite finds problems effectively as early as possible, long before the software reaches a customer, and even before it reaches the QA team.
*Virtually unlimited iterations of test case execution
*Support for Agile and extreme development methodologies
*Disciplined documentation of test cases
*Customized defect reporting
*Finding defects missed by manual testing

The challenge is in extending these advantages to GUI testing.

==GUI testing in Ruby and Rails==

Ruby prefers the term scripted testing over the more traditional automated testing. For testing a GUI application there can be several kind of tests in the background to verify the functionality and requirements of an application.

Various frameworks that support testing in Ruby are:
* Test:Unit - It is a unit testing framework for Ruby.
* Capybara[https://github.com/jnicklas/capybara] - It is an integration testing tool for web applications.
* Rspec[http://rspec.info/] - Behaviour Driven Development (BDD) framework/ test tool
* Cucumber[https://github.com/cucumber/cucumber] - It is a tool for running automated acceptance tests written in a behavior-driven development (BDD) style

Ruby on Rails testing frameworks are much more advanced than other web frameworks.

==GUI Testing - Pitfalls==
*Coverage criteria cannot be determined accurately with GUI testing.
*Verifying whether the GUI test executes correctly poses a problem as the logging is difficult.
*Developing a stable regression suite is difficult since simple changes in GUI can render the test suite obsolete.

==GUI Testing Tools==

GUI testing tools serve the purpose of automating the testing process of software with graphical user interfaces. Following are few of the available open source GUI testing tools:

*AutoHotkey
*CubicTest
*Dogtail
*Dojo
*Selenium
*Watir
*GNU Xnee
*Sikuli

==Selenium==

===Introduction===
Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language (Selenium IDE). It also provides a test domain-specific language (Selenese) to write tests in a number of popular programming languages, including Java, C#, [http://groovy.codehaus.org/ Groovy], Perl, PHP, Python and Ruby. The tests can then be run against most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.

===Selenium Tool Suite===
Selenium is composed of multiple software tools.

====Selenium IDE====
*Prototyping tool for building testscripts.
*Firefox plugin provides easy to use interface for developing automated tests.
*Supports 'record and play' feature to create reusable scripts for testing.

====Selenium1====
*Also known as Selenium RC or Remote Control
*Provides flexibility in porting tests across browsers and platforms.
*Currently in maintainence mode. No active development.

====Selenium 2====
*Also known as Selenium Webdriver
*Supports WebDriver API thus providing maximum flexibility in porting the tests.
*Runs Selenium 1’s Selenium RC interface for backwards compatibility.

====Selenium Grid====
*Selenium-Grid allows the Selenium RC solution to scale for large test suites and for test suites that must be run in multiple environments.
*Selenium Grid runs the tests in parallel, that is, different tests can be run at the same time on different remote machines.
*Selenium Grid greatly improves the time it takes to run the suite by making use of parallel processing.

===Supported Browsers and Platforms===

====Selenium 2====
*Google Chrome 12.0.712.0+
*Internet Explorer 6, 7, 8, 9 - 32 and 64-bit where applicable
*Firefox 3.0, 3.5, 3.6, 4.0, 5.0, 6, 7
*Opera 11.5+
*HtmlUnit 2.9
*Android – 2.3+ for phones and tablets (devices & emulators)
*iOS 3+ for phones (devices & emulators) and 3.2+ for tablets (devices & emulators)

====Selenium 1 and Selenium IDE====
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Browser'''
| align="center" style="background:#f0f0f0;"|'''Selenium IDE'''
| align="center" style="background:#f0f0f0;"|'''Selenium 1 (RC)'''
| align="center" style="background:#f0f0f0;"|'''Operating Systems'''
|-
| Firefox 2, 3||Record and playback tests ||Start browser, run tests||Windows, Linux, Mac
|-
| IE 6, 7, 8||Unsupported ||Start browser, run tests||Windows
|-
| Safari 2, 3, 4||Unsupported ||Start browser, run tests||Windows, Mac
|-
| Opera 8, 9, 10||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
| Google Chrome||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
|}

===Advantages===
The chief advantages of Selenium are :
*Flexibility - Test automation can be customized by adding functionality to Selenium test scripts and Selenium framework.
*Open Source - The source code can be downloaded and modified as needed to suit new browsers.
*Deploys on multiple paltforms - Windows, Linux, and Macintosh.

===Disadvantages===
*Identifying the locators and common attributes like id, names etc as well as XPATH, javascript DOM and others is difficult.
*Results are not available in good detail. Debugging failures migt prove to be difficult sometimes.
*Loop and data driven testing is not supported by Selenium IDE.
*Options to verify the images are not available.

==Auto Hot Key==
AutoHotkey automates tests by sending keystrokes and mouse clicks to the target application with the help of a macro recorder.
Virtually any key, button, or combination can become a hotkey.
Following are the notable features of hotkey:
* Expand abbreviations as you type them. For example, typing "gn" can automatically produce "good night".
* Create custom data-entry forms, user interfaces, and menu bars.
* Remap keys and buttons on your keyboard, joystick, and mouse.
* Convert any script into an EXE file that can be run on computers that don't have AutoHotkey installed.

Quick start tutorial : http://www.autohotkey.com/docs/Tutorial.htm

==Watir==
Watir, pronounced water, stands for Web Application Testing in Ruby. Watir is an open-source (BSD) family of Ruby libraries for automating web browsers. It is distributed as a Ruby GEM named 'Watir'. Watir drives browsers the same way people do. It clicks links, fills in forms, presses buttons. Watir also checks results, such as whether expected text appears on the page or not.

There are 2 version available :
* Watir-Classic : supports only Internet Explorer on Windows
* Watir-WebDriver : supports Chrome, Firefox, Internet Explorer, Opera and also running in headless mode (HTMLUnit).

==GNU Xnee==
GNU Xnee is a suite of programs that can record, replay and distribute user actions under the X11 environment. Xnee has the capability to :
* Automate tests like nightly regression
* Demonstrate programs by recording and replaying a user interaction with the system
* Distribute actions from system admin to end users.

The Record and replay ‘macro’ is the highlight of Xnee.

==DOJO==
Dojo is a JavaScript framework targeting the many needs of large-scale client-side web development.

* Dojo abstracts the differences among diverse browsers to provide APIs that will work on all of them (it can even run on the server under Node.js)
* It establishes a framework for defining modules of code and managing their inter-dependencies
* Supports internationalization, localization, and accessibility
* Provides a rich suite of commonly needed utility classes and user-interface widgets.

==CubicTest==
CubicTest is a graphical Eclipse plug-in for writing Selenium and Watir tests. It makes tests faster and easier to write, and provides abstractions to make tests more robust and reusable.

* CubicTest's test editor is centered around pages/states and transitions between these pages/states.
* The model is intuitive for both Ajax and traditional web applications and supports most user interaction types.
* CubicTest features an innovative test recorder and test runner based on Selenium RC which are fully integrated with the graphical test editor.

==Dogtail==
Dogtail is a GUI test tool and automation framework written in Python. It uses Accessibility (a11y) technologies to communicate with desktop applications. Dogtail scripts are written in Python and executed like any other Python program.
Follwoing are the notable features of Dogtail:
* Object-Oriented API: With the object oriented API, you are under control of the UI tree and its elements, allowing you to write sophisticated scripts utilizing benefits of OO right deep from dogtail.
* Procedural API: Ace programmer credentials are not necessary to write useful automated scripts with procedural API.
* Easily Extensible: Writing custom classes and helper libraries are easy.
* Results and debug reporting: Separate logs for test case comparisons and debug information are generated.

==Sikuli==
Sikuli automates GUI testing by using image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code.
* Sikuli uses an innovative approach of automating GUI tests by using screenshots and powerpoint slides.
* Sikuli Script is a visual scripting API using [http://en.wikipedia.org/wiki/Jython Jython] to create automation scripts.
* Sikuli includes an integrated development environment (IDE) for writing visual Sikuli scripts with screenshots.

==See Also==
* Web testing tools [http://en.wikipedia.org/wiki/List_of_web_testing_tools]
* Selenium Framework [http://www.mediawiki.org/wiki/Selenium_Framework]
* Selenium [http://www.jroller.com/selenium/]
* Using Selenium [http://aspyct.org/blog/2012/09/09/functional-web-testing-with-selenium-and-ruby/]
* Selenium by example [http://learnseleniumautomation.blogspot.in/2012/08/learn-selenium-webdriver-by-example.html]

==References==
*http://docs.seleniumhq.org/docs/
*http://www.eecs.yorku.ca/course_archive/2004-05/W/4313/Slides/Module10-GUI.pdf - 2004-05
*http://www.cs.helsinki.fi/u/paakki/mikkolainen.pdf
*http://watir.com/
*http://www.gnu.org/software/xnee/
*https://fedorahosted.org/dogtail/
*http://www.cubictest.org/
*http://www.autohotkey.com/
*http://www.sikuli.org/
*http://sivaeluri.blogspot.com/2012/08/advantages-and-disadvantages-of.html
*http://dojotoolkit.org/reference-guide/1.9/util/dohrobot.html
*http://cvs.cs.umd.edu/~atif/papers/MemonIEEEComputer2002.pdf - 2000

==Note to reviewers==
The topic is very vast. Hence the wiki is written based on the guidelines provided by the TA's and the Prof.
* List all GUI tools used in OSS that you can quickly identify.
* Try to describe the tools to the same level of detail, except that you may choose to go into more detail on tools that are used with Rails.
* Listing of commands is not a good idea. You are not writing a reference manual; you are writing a descriptive article that someone might read to learn about what's available before choosing a tool or tools. You should aim for readability.

We have referred the respective tool websites to provide the overview for each one of them. We have provided appropriate citations as well. Additionally the tool and the documentation itself are under GNU/ open source licence and hence will not fall under copyright violation. Please correct us if we are wrong.

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-15T02:07:59Z

Vshesha: /* Introduction */

=='''OPEN SOURCE GUI TESTING TOOLS'''==
==Introduction==
Graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its designed specifications.

GUI testing is difficult mainly due to following reasons :
* Large space of possibilities. Each sequence of GUI commands can result in various states. Evaluation of all these states is essential for validation of the GUI of the given software.
*[http://en.wikipedia.org/wiki/Event-driven_architecture Event-driven architecture]. The test suite has to simulate the various user created actions.

Following are the challenges encountered while testing the graphical user interface of any software or system:
* Automation is difficult.
* The scope for testing is enormous
* Inability to determine the state of the program from GUI.
* [http://en.wikipedia.org/wiki/Regression_testing Regression testing] is difficult. Testcases may not be reusable

The current trend in user interfaces is geared towards graphical user interfaces (GUIs). This presents a problem for designing tests for software, since GUIs are very complex and hence GUI testing is very time consuming. Automation is a requirement for testing any larger graphical user interfaces, but automating GUI tests is not a straightforward task. Techniques which are familiar from the command line interface (CLI) age, don’t translate to the GUI world without problems.

==Test Automation==

The advantages of test automation are as follows.
*Frequent regression testing
*Rapid feedback to developers - The earlier the problems are found, the cheaper it is to fix them. An automated unit test suite finds problems effectively as early as possible, long before the software reaches a customer, and even before it reaches the QA team.
*Virtually unlimited iterations of test case execution
*Support for Agile and extreme development methodologies
*Disciplined documentation of test cases
*Customized defect reporting
*Finding defects missed by manual testing

The challenge is in extending these advantages to GUI testing.

==GUI testing in Ruby and Rails==

Ruby prefers the term scripted testing over the more traditional automated testing. For testing a GUI application there can be several kind of tests in the background to verify the functionality and requirements of an application.

Various frameworks that support testing in Ruby are:
* Test:Unit - It is a unit testing framework for Ruby.
* Capybara[https://github.com/jnicklas/capybara] - It is an integration testing tool for web applications.
* Rspec[http://rspec.info/] - Behaviour Driven Development (BDD) framework/ test tool
* Cucumber[https://github.com/cucumber/cucumber] - It is a tool for running automated acceptance tests written in a behavior-driven development (BDD) style

Ruby on Rails testing frameworks are much more advanced than other web frameworks.

==GUI Testing - Pitfalls==
*Coverage criteria cannot be determined accurately with GUI testing.
*Verifying whether the GUI test executes correctly poses a problem as the logging is difficult.
*Developing a stable regression suite is difficult since simple changes in GUI can render the test suite obsolete.

==GUI Testing Tools==

GUI testing tools serve the purpose of automating the testing process of software with graphical user interfaces. Following are few of the available open source GUI testing tools:

*AutoHotkey
*CubicTest
*Dogtail
*Dojo
*Selenium
*Watir
*GNU Xnee
*Sikuli

==Selenium==

===Introduction===
Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language (Selenium IDE). It also provides a test domain-specific language (Selenese) to write tests in a number of popular programming languages, including Java, C#, [http://groovy.codehaus.org/ Groovy], Perl, PHP, Python and Ruby. The tests can then be run against most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.

===Selenium Tool Suite===
Selenium is composed of multiple software tools.

====Selenium IDE====
*Prototyping tool for building testscripts.
*Firefox plugin provides easy to use interface for developing automated tests.
*Supports 'record and play' feature to create reusable scripts for testing.

====Selenium1====
*Also known as Selenium RC or Remote Control
*Provides flexibility in porting tests across browsers and platforms.
*Currently in maintainence mode. No active development.

====Selenium 2====
*Also known as Selenium Webdriver
*Supports WebDriver API thus providing maximum flexibility in porting the tests.
*Runs Selenium 1’s Selenium RC interface for backwards compatibility.

====Selenium Grid====
*Selenium-Grid allows the Selenium RC solution to scale for large test suites and for test suites that must be run in multiple environments.
*Selenium Grid runs the tests in parallel, that is, different tests can be run at the same time on different remote machines.
*Selenium Grid greatly improves the time it takes to run the suite by making use of parallel processing.

===Supported Browsers and Platforms===

====Selenium 2====
*Google Chrome 12.0.712.0+
*Internet Explorer 6, 7, 8, 9 - 32 and 64-bit where applicable
*Firefox 3.0, 3.5, 3.6, 4.0, 5.0, 6, 7
*Opera 11.5+
*HtmlUnit 2.9
*Android – 2.3+ for phones and tablets (devices & emulators)
*iOS 3+ for phones (devices & emulators) and 3.2+ for tablets (devices & emulators)

====Selenium 1 and Selenium IDE====
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Browser'''
| align="center" style="background:#f0f0f0;"|'''Selenium IDE'''
| align="center" style="background:#f0f0f0;"|'''Selenium 1 (RC)'''
| align="center" style="background:#f0f0f0;"|'''Operating Systems'''
|-
| Firefox 2, 3||Record and playback tests ||Start browser, run tests||Windows, Linux, Mac
|-
| IE 6, 7, 8||Unsupported ||Start browser, run tests||Windows
|-
| Safari 2, 3, 4||Unsupported ||Start browser, run tests||Windows, Mac
|-
| Opera 8, 9, 10||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
| Google Chrome||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
|}

===Advantages===
The chief advantages of Selenium are :
*Flexibility - Test automation can be customized by adding functionality to Selenium test scripts and Selenium framework.
*Open Source - The source code can be downloaded and modified as needed to suit new browsers.
*Deploys on multiple paltforms - Windows, Linux, and Macintosh.

===Disadvantages===
*Identifying the locators and common attributes like id, names etc as well as XPATH, javascript DOM and others is difficult.
*Results are not available in good detail. Debugging failures migt prove to be difficult sometimes.
*Loop and data driven testing is not supported by Selenium IDE.
*Options to verify the images are not available.

==Auto Hot Key==
AutoHotkey automates tests by sending keystrokes and mouse clicks to the target application with the help of a macro recorder.
Virtually any key, button, or combination can become a hotkey.
Following are the notable features of hotkey:
* Expand abbreviations as you type them. For example, typing "gn" can automatically produce "good night".
* Create custom data-entry forms, user interfaces, and menu bars.
* Remap keys and buttons on your keyboard, joystick, and mouse.
* Convert any script into an EXE file that can be run on computers that don't have AutoHotkey installed.

Quick start tutorial : http://www.autohotkey.com/docs/Tutorial.htm

==Watir==
Watir, pronounced water, stands for Web Application Testing in Ruby. Watir is an open-source (BSD) family of Ruby libraries for automating web browsers. It is distributed as a Ruby GEM named 'Watir'. Watir drives browsers the same way people do. It clicks links, fills in forms, presses buttons. Watir also checks results, such as whether expected text appears on the page or not.

There are 2 version available :
* Watir-Classic : supports only Internet Explorer on Windows
* Watir-WebDriver : supports Chrome, Firefox, Internet Explorer, Opera and also running in headless mode (HTMLUnit).

==GNU Xnee==
GNU Xnee is a suite of programs that can record, replay and distribute user actions under the X11 environment. Xnee has the capability to :
* Automate tests like nightly regression
* Demonstrate programs by recording and replaying a user interaction with the system
* Distribute actions from system admin to end users.

The Record and replay ‘macro’ is the highlight of Xnee.

==DOJO==
Dojo is a JavaScript framework targeting the many needs of large-scale client-side web development.

* Dojo abstracts the differences among diverse browsers to provide APIs that will work on all of them (it can even run on the server under Node.js)
* It establishes a framework for defining modules of code and managing their inter-dependencies
* Supports internationalization, localization, and accessibility
* Provides a rich suite of commonly needed utility classes and user-interface widgets.

==CubicTest==
CubicTest is a graphical Eclipse plug-in for writing Selenium and Watir tests. It makes tests faster and easier to write, and provides abstractions to make tests more robust and reusable.

* CubicTest's test editor is centered around pages/states and transitions between these pages/states.
* The model is intuitive for both Ajax and traditional web applications and supports most user interaction types.
* CubicTest features an innovative test recorder and test runner based on Selenium RC which are fully integrated with the graphical test editor.

==Dogtail==
Dogtail is a GUI test tool and automation framework written in Python. It uses Accessibility (a11y) technologies to communicate with desktop applications. Dogtail scripts are written in Python and executed like any other Python program.
Follwoing are the notable features of Dogtail:
* Object-Oriented API: With the object oriented API, you are under control of the UI tree and its elements, allowing you to write sophisticated scripts utilizing benefits of OO right deep from dogtail.
* Procedural API: Ace programmer credentials are not necessary to write useful automated scripts with procedural API.
* Easily Extensible: Writing custom classes and helper libraries are easy.
* Results and debug reporting: Separate logs for test case comparisons and debug information are generated.

==Sikuli==
Sikuli automates GUI testing by using image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code.
* Sikuli uses an innovative approach of automating GUI tests by using screenshots and powerpoint slides.
* Sikuli Script is a visual scripting API using [http://en.wikipedia.org/wiki/Jython Jython] to create automation scripts.
* Sikuli includes an integrated development environment (IDE) for writing visual Sikuli scripts with screenshots.

==See Also==
* Web testing tools [http://en.wikipedia.org/wiki/List_of_web_testing_tools]
* Selenium Framework [http://www.mediawiki.org/wiki/Selenium_Framework]
* Selenium [http://www.jroller.com/selenium/]
* Using Selenium [http://aspyct.org/blog/2012/09/09/functional-web-testing-with-selenium-and-ruby/]
* Selenium by example [http://learnseleniumautomation.blogspot.in/2012/08/learn-selenium-webdriver-by-example.html]

==References==
*http://docs.seleniumhq.org/docs/
*http://www.eecs.yorku.ca/course_archive/2004-05/W/4313/Slides/Module10-GUI.pdf - 2004-05
*http://www.cs.helsinki.fi/u/paakki/mikkolainen.pdf
*http://watir.com/
*http://www.gnu.org/software/xnee/
*https://fedorahosted.org/dogtail/
*http://www.cubictest.org/
*http://www.autohotkey.com/
*http://www.sikuli.org/
*http://sivaeluri.blogspot.com/2012/08/advantages-and-disadvantages-of.html
*http://dojotoolkit.org/reference-guide/1.9/util/dohrobot.html
*http://cvs.cs.umd.edu/~atif/papers/MemonIEEEComputer2002.pdf - 2000

==Note to reviewers==
The topic is very vast. Hence the wiki is written based on the guidelines provided by the TA's and the Prof.
* List all GUI tools used in OSS that you can quickly identify.
* Try to describe the tools to the same level of detail, except that you may choose to go into more detail on tools that are used with Rails.
* Listing of commands is not a good idea. You are not writing a reference manual; you are writing a descriptive article that someone might read to learn about what's available before choosing a tool or tools. You should aim for readability.

We have referred the respective tool websites to provide the overview for each one of them. We have provided appropriate citations as well. Additionally the tool and the documentation itself are under GNU/ open source licence and hence will not fall under copyright violation. Please correct us if we are wrong.

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-15T02:02:03Z

Vshesha: /* References */

==Introduction==
Graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its designed specifications.

GUI testing is difficult mainly due to following reasons :
* Large space of possibilities. Each sequence of GUI commands can result in various states. Evaluation of all these states is essential for validation of the GUI of the given software.
*[http://en.wikipedia.org/wiki/Event-driven_architecture Event-driven architecture]. The test suite has to simulate the various user created actions.

Following are the challenges encountered while testing the graphical user interface of any software or system:
* Automation is difficult.
* The scope for testing is enormous
* Inability to determine the state of the program from GUI.
* [http://en.wikipedia.org/wiki/Regression_testing Regression testing] is difficult. Testcases may not be reusable

The current trend in user interfaces is geared towards graphical user interfaces (GUIs). This presents a problem for designing tests for software, since GUIs are very complex and hence GUI testing is very time consuming. Automation is a requirement for testing any larger graphical user interfaces, but automating GUI tests is not a straightforward task. Techniques which are familiar from the command line interface (CLI) age, don’t translate to the GUI world without problems.

==Test Automation==

The advantages of test automation are as follows.
*Frequent regression testing
*Rapid feedback to developers - The earlier the problems are found, the cheaper it is to fix them. An automated unit test suite finds problems effectively as early as possible, long before the software reaches a customer, and even before it reaches the QA team.
*Virtually unlimited iterations of test case execution
*Support for Agile and extreme development methodologies
*Disciplined documentation of test cases
*Customized defect reporting
*Finding defects missed by manual testing

The challenge is in extending these advantages to GUI testing.

==GUI testing in Ruby and Rails==

Ruby prefers the term scripted testing over the more traditional automated testing. For testing a GUI application there can be several kind of tests in the background to verify the functionality and requirements of an application.

Various frameworks that support testing in Ruby are:
* Test:Unit - It is a unit testing framework for Ruby.
* Capybara[https://github.com/jnicklas/capybara] - It is an integration testing tool for web applications.
* Rspec[http://rspec.info/] - Behaviour Driven Development (BDD) framework/ test tool
* Cucumber[https://github.com/cucumber/cucumber] - It is a tool for running automated acceptance tests written in a behavior-driven development (BDD) style

Ruby on Rails testing frameworks are much more advanced than other web frameworks.

==GUI Testing - Pitfalls==
*Coverage criteria cannot be determined accurately with GUI testing.
*Verifying whether the GUI test executes correctly poses a problem as the logging is difficult.
*Developing a stable regression suite is difficult since simple changes in GUI can render the test suite obsolete.

==GUI Testing Tools==

GUI testing tools serve the purpose of automating the testing process of software with graphical user interfaces. Following are few of the available open source GUI testing tools:

*AutoHotkey
*CubicTest
*Dogtail
*Dojo
*Selenium
*Watir
*GNU Xnee
*Sikuli

==Selenium==

===Introduction===
Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language (Selenium IDE). It also provides a test domain-specific language (Selenese) to write tests in a number of popular programming languages, including Java, C#, [http://groovy.codehaus.org/ Groovy], Perl, PHP, Python and Ruby. The tests can then be run against most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.

===Selenium Tool Suite===
Selenium is composed of multiple software tools.

====Selenium IDE====
*Prototyping tool for building testscripts.
*Firefox plugin provides easy to use interface for developing automated tests.
*Supports 'record and play' feature to create reusable scripts for testing.

====Selenium1====
*Also known as Selenium RC or Remote Control
*Provides flexibility in porting tests across browsers and platforms.
*Currently in maintainence mode. No active development.

====Selenium 2====
*Also known as Selenium Webdriver
*Supports WebDriver API thus providing maximum flexibility in porting the tests.
*Runs Selenium 1’s Selenium RC interface for backwards compatibility.

====Selenium Grid====
*Selenium-Grid allows the Selenium RC solution to scale for large test suites and for test suites that must be run in multiple environments.
*Selenium Grid runs the tests in parallel, that is, different tests can be run at the same time on different remote machines.
*Selenium Grid greatly improves the time it takes to run the suite by making use of parallel processing.

===Supported Browsers and Platforms===

====Selenium 2====
*Google Chrome 12.0.712.0+
*Internet Explorer 6, 7, 8, 9 - 32 and 64-bit where applicable
*Firefox 3.0, 3.5, 3.6, 4.0, 5.0, 6, 7
*Opera 11.5+
*HtmlUnit 2.9
*Android – 2.3+ for phones and tablets (devices & emulators)
*iOS 3+ for phones (devices & emulators) and 3.2+ for tablets (devices & emulators)

====Selenium 1 and Selenium IDE====
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Browser'''
| align="center" style="background:#f0f0f0;"|'''Selenium IDE'''
| align="center" style="background:#f0f0f0;"|'''Selenium 1 (RC)'''
| align="center" style="background:#f0f0f0;"|'''Operating Systems'''
|-
| Firefox 2, 3||Record and playback tests ||Start browser, run tests||Windows, Linux, Mac
|-
| IE 6, 7, 8||Unsupported ||Start browser, run tests||Windows
|-
| Safari 2, 3, 4||Unsupported ||Start browser, run tests||Windows, Mac
|-
| Opera 8, 9, 10||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
| Google Chrome||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
|}

===Advantages===
The chief advantages of Selenium are :
*Flexibility - Test automation can be customized by adding functionality to Selenium test scripts and Selenium framework.
*Open Source - The source code can be downloaded and modified as needed to suit new browsers.
*Deploys on multiple paltforms - Windows, Linux, and Macintosh.

===Disadvantages===
*Identifying the locators and common attributes like id, names etc as well as XPATH, javascript DOM and others is difficult.
*Results are not available in good detail. Debugging failures migt prove to be difficult sometimes.
*Loop and data driven testing is not supported by Selenium IDE.
*Options to verify the images are not available.

==Auto Hot Key==
AutoHotkey automates tests by sending keystrokes and mouse clicks to the target application with the help of a macro recorder.
Virtually any key, button, or combination can become a hotkey.
Following are the notable features of hotkey:
* Expand abbreviations as you type them. For example, typing "gn" can automatically produce "good night".
* Create custom data-entry forms, user interfaces, and menu bars.
* Remap keys and buttons on your keyboard, joystick, and mouse.
* Convert any script into an EXE file that can be run on computers that don't have AutoHotkey installed.

Quick start tutorial : http://www.autohotkey.com/docs/Tutorial.htm

==Watir==
Watir, pronounced water, stands for Web Application Testing in Ruby. Watir is an open-source (BSD) family of Ruby libraries for automating web browsers. It is distributed as a Ruby GEM named 'Watir'. Watir drives browsers the same way people do. It clicks links, fills in forms, presses buttons. Watir also checks results, such as whether expected text appears on the page or not.

There are 2 version available :
* Watir-Classic : supports only Internet Explorer on Windows
* Watir-WebDriver : supports Chrome, Firefox, Internet Explorer, Opera and also running in headless mode (HTMLUnit).

==GNU Xnee==
GNU Xnee is a suite of programs that can record, replay and distribute user actions under the X11 environment. Xnee has the capability to :
* Automate tests like nightly regression
* Demonstrate programs by recording and replaying a user interaction with the system
* Distribute actions from system admin to end users.

The Record and replay ‘macro’ is the highlight of Xnee.

==DOJO==
Dojo is a JavaScript framework targeting the many needs of large-scale client-side web development.

* Dojo abstracts the differences among diverse browsers to provide APIs that will work on all of them (it can even run on the server under Node.js)
* It establishes a framework for defining modules of code and managing their inter-dependencies
* Supports internationalization, localization, and accessibility
* Provides a rich suite of commonly needed utility classes and user-interface widgets.

==CubicTest==
CubicTest is a graphical Eclipse plug-in for writing Selenium and Watir tests. It makes tests faster and easier to write, and provides abstractions to make tests more robust and reusable.

* CubicTest's test editor is centered around pages/states and transitions between these pages/states.
* The model is intuitive for both Ajax and traditional web applications and supports most user interaction types.
* CubicTest features an innovative test recorder and test runner based on Selenium RC which are fully integrated with the graphical test editor.

==Dogtail==
Dogtail is a GUI test tool and automation framework written in Python. It uses Accessibility (a11y) technologies to communicate with desktop applications. Dogtail scripts are written in Python and executed like any other Python program.
Follwoing are the notable features of Dogtail:
* Object-Oriented API: With the object oriented API, you are under control of the UI tree and its elements, allowing you to write sophisticated scripts utilizing benefits of OO right deep from dogtail.
* Procedural API: Ace programmer credentials are not necessary to write useful automated scripts with procedural API.
* Easily Extensible: Writing custom classes and helper libraries are easy.
* Results and debug reporting: Separate logs for test case comparisons and debug information are generated.

==Sikuli==
Sikuli automates GUI testing by using image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code.
* Sikuli uses an innovative approach of automating GUI tests by using screenshots and powerpoint slides.
* Sikuli Script is a visual scripting API using [http://en.wikipedia.org/wiki/Jython Jython] to create automation scripts.
* Sikuli includes an integrated development environment (IDE) for writing visual Sikuli scripts with screenshots.

==See Also==
* Web testing tools [http://en.wikipedia.org/wiki/List_of_web_testing_tools]
* Selenium Framework [http://www.mediawiki.org/wiki/Selenium_Framework]
* Selenium [http://www.jroller.com/selenium/]
* Using Selenium [http://aspyct.org/blog/2012/09/09/functional-web-testing-with-selenium-and-ruby/]
* Selenium by example [http://learnseleniumautomation.blogspot.in/2012/08/learn-selenium-webdriver-by-example.html]

==References==
*http://docs.seleniumhq.org/docs/
*http://www.eecs.yorku.ca/course_archive/2004-05/W/4313/Slides/Module10-GUI.pdf - 2004-05
*http://www.cs.helsinki.fi/u/paakki/mikkolainen.pdf
*http://watir.com/
*http://www.gnu.org/software/xnee/
*https://fedorahosted.org/dogtail/
*http://www.cubictest.org/
*http://www.autohotkey.com/
*http://www.sikuli.org/
*http://sivaeluri.blogspot.com/2012/08/advantages-and-disadvantages-of.html
*http://dojotoolkit.org/reference-guide/1.9/util/dohrobot.html
*http://cvs.cs.umd.edu/~atif/papers/MemonIEEEComputer2002.pdf - 2000

==Note to reviewers==
The topic is very vast. Hence the wiki is written based on the guidelines provided by the TA's and the Prof.
* List all GUI tools used in OSS that you can quickly identify.
* Try to describe the tools to the same level of detail, except that you may choose to go into more detail on tools that are used with Rails.
* Listing of commands is not a good idea. You are not writing a reference manual; you are writing a descriptive article that someone might read to learn about what's available before choosing a tool or tools. You should aim for readability.

We have referred the respective tool websites to provide the overview for each one of them. We have provided appropriate citations as well. Additionally the tool and the documentation itself are under GNU/ open source licence and hence will not fall under copyright violation. Please correct us if we are wrong.

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-15T02:00:51Z

Vshesha: /* References */

==Introduction==
Graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its designed specifications.

GUI testing is difficult mainly due to following reasons :
* Large space of possibilities. Each sequence of GUI commands can result in various states. Evaluation of all these states is essential for validation of the GUI of the given software.
*[http://en.wikipedia.org/wiki/Event-driven_architecture Event-driven architecture]. The test suite has to simulate the various user created actions.

Following are the challenges encountered while testing the graphical user interface of any software or system:
* Automation is difficult.
* The scope for testing is enormous
* Inability to determine the state of the program from GUI.
* [http://en.wikipedia.org/wiki/Regression_testing Regression testing] is difficult. Testcases may not be reusable

The current trend in user interfaces is geared towards graphical user interfaces (GUIs). This presents a problem for designing tests for software, since GUIs are very complex and hence GUI testing is very time consuming. Automation is a requirement for testing any larger graphical user interfaces, but automating GUI tests is not a straightforward task. Techniques which are familiar from the command line interface (CLI) age, don’t translate to the GUI world without problems.

==Test Automation==

The advantages of test automation are as follows.
*Frequent regression testing
*Rapid feedback to developers - The earlier the problems are found, the cheaper it is to fix them. An automated unit test suite finds problems effectively as early as possible, long before the software reaches a customer, and even before it reaches the QA team.
*Virtually unlimited iterations of test case execution
*Support for Agile and extreme development methodologies
*Disciplined documentation of test cases
*Customized defect reporting
*Finding defects missed by manual testing

The challenge is in extending these advantages to GUI testing.

==GUI testing in Ruby and Rails==

Ruby prefers the term scripted testing over the more traditional automated testing. For testing a GUI application there can be several kind of tests in the background to verify the functionality and requirements of an application.

Various frameworks that support testing in Ruby are:
* Test:Unit - It is a unit testing framework for Ruby.
* Capybara[https://github.com/jnicklas/capybara] - It is an integration testing tool for web applications.
* Rspec[http://rspec.info/] - Behaviour Driven Development (BDD) framework/ test tool
* Cucumber[https://github.com/cucumber/cucumber] - It is a tool for running automated acceptance tests written in a behavior-driven development (BDD) style

Ruby on Rails testing frameworks are much more advanced than other web frameworks.

==GUI Testing - Pitfalls==
*Coverage criteria cannot be determined accurately with GUI testing.
*Verifying whether the GUI test executes correctly poses a problem as the logging is difficult.
*Developing a stable regression suite is difficult since simple changes in GUI can render the test suite obsolete.

==GUI Testing Tools==

GUI testing tools serve the purpose of automating the testing process of software with graphical user interfaces. Following are few of the available open source GUI testing tools:

*AutoHotkey
*CubicTest
*Dogtail
*Dojo
*Selenium
*Watir
*GNU Xnee
*Sikuli

==Selenium==

===Introduction===
Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language (Selenium IDE). It also provides a test domain-specific language (Selenese) to write tests in a number of popular programming languages, including Java, C#, [http://groovy.codehaus.org/ Groovy], Perl, PHP, Python and Ruby. The tests can then be run against most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.

===Selenium Tool Suite===
Selenium is composed of multiple software tools.

====Selenium IDE====
*Prototyping tool for building testscripts.
*Firefox plugin provides easy to use interface for developing automated tests.
*Supports 'record and play' feature to create reusable scripts for testing.

====Selenium1====
*Also known as Selenium RC or Remote Control
*Provides flexibility in porting tests across browsers and platforms.
*Currently in maintainence mode. No active development.

====Selenium 2====
*Also known as Selenium Webdriver
*Supports WebDriver API thus providing maximum flexibility in porting the tests.
*Runs Selenium 1’s Selenium RC interface for backwards compatibility.

====Selenium Grid====
*Selenium-Grid allows the Selenium RC solution to scale for large test suites and for test suites that must be run in multiple environments.
*Selenium Grid runs the tests in parallel, that is, different tests can be run at the same time on different remote machines.
*Selenium Grid greatly improves the time it takes to run the suite by making use of parallel processing.

===Supported Browsers and Platforms===

====Selenium 2====
*Google Chrome 12.0.712.0+
*Internet Explorer 6, 7, 8, 9 - 32 and 64-bit where applicable
*Firefox 3.0, 3.5, 3.6, 4.0, 5.0, 6, 7
*Opera 11.5+
*HtmlUnit 2.9
*Android – 2.3+ for phones and tablets (devices & emulators)
*iOS 3+ for phones (devices & emulators) and 3.2+ for tablets (devices & emulators)

====Selenium 1 and Selenium IDE====
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Browser'''
| align="center" style="background:#f0f0f0;"|'''Selenium IDE'''
| align="center" style="background:#f0f0f0;"|'''Selenium 1 (RC)'''
| align="center" style="background:#f0f0f0;"|'''Operating Systems'''
|-
| Firefox 2, 3||Record and playback tests ||Start browser, run tests||Windows, Linux, Mac
|-
| IE 6, 7, 8||Unsupported ||Start browser, run tests||Windows
|-
| Safari 2, 3, 4||Unsupported ||Start browser, run tests||Windows, Mac
|-
| Opera 8, 9, 10||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
| Google Chrome||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
|}

===Advantages===
The chief advantages of Selenium are :
*Flexibility - Test automation can be customized by adding functionality to Selenium test scripts and Selenium framework.
*Open Source - The source code can be downloaded and modified as needed to suit new browsers.
*Deploys on multiple paltforms - Windows, Linux, and Macintosh.

===Disadvantages===
*Identifying the locators and common attributes like id, names etc as well as XPATH, javascript DOM and others is difficult.
*Results are not available in good detail. Debugging failures migt prove to be difficult sometimes.
*Loop and data driven testing is not supported by Selenium IDE.
*Options to verify the images are not available.

==Auto Hot Key==
AutoHotkey automates tests by sending keystrokes and mouse clicks to the target application with the help of a macro recorder.
Virtually any key, button, or combination can become a hotkey.
Following are the notable features of hotkey:
* Expand abbreviations as you type them. For example, typing "gn" can automatically produce "good night".
* Create custom data-entry forms, user interfaces, and menu bars.
* Remap keys and buttons on your keyboard, joystick, and mouse.
* Convert any script into an EXE file that can be run on computers that don't have AutoHotkey installed.

Quick start tutorial : http://www.autohotkey.com/docs/Tutorial.htm

==Watir==
Watir, pronounced water, stands for Web Application Testing in Ruby. Watir is an open-source (BSD) family of Ruby libraries for automating web browsers. It is distributed as a Ruby GEM named 'Watir'. Watir drives browsers the same way people do. It clicks links, fills in forms, presses buttons. Watir also checks results, such as whether expected text appears on the page or not.

There are 2 version available :
* Watir-Classic : supports only Internet Explorer on Windows
* Watir-WebDriver : supports Chrome, Firefox, Internet Explorer, Opera and also running in headless mode (HTMLUnit).

==GNU Xnee==
GNU Xnee is a suite of programs that can record, replay and distribute user actions under the X11 environment. Xnee has the capability to :
* Automate tests like nightly regression
* Demonstrate programs by recording and replaying a user interaction with the system
* Distribute actions from system admin to end users.

The Record and replay ‘macro’ is the highlight of Xnee.

==DOJO==
Dojo is a JavaScript framework targeting the many needs of large-scale client-side web development.

* Dojo abstracts the differences among diverse browsers to provide APIs that will work on all of them (it can even run on the server under Node.js)
* It establishes a framework for defining modules of code and managing their inter-dependencies
* Supports internationalization, localization, and accessibility
* Provides a rich suite of commonly needed utility classes and user-interface widgets.

==CubicTest==
CubicTest is a graphical Eclipse plug-in for writing Selenium and Watir tests. It makes tests faster and easier to write, and provides abstractions to make tests more robust and reusable.

* CubicTest's test editor is centered around pages/states and transitions between these pages/states.
* The model is intuitive for both Ajax and traditional web applications and supports most user interaction types.
* CubicTest features an innovative test recorder and test runner based on Selenium RC which are fully integrated with the graphical test editor.

==Dogtail==
Dogtail is a GUI test tool and automation framework written in Python. It uses Accessibility (a11y) technologies to communicate with desktop applications. Dogtail scripts are written in Python and executed like any other Python program.
Follwoing are the notable features of Dogtail:
* Object-Oriented API: With the object oriented API, you are under control of the UI tree and its elements, allowing you to write sophisticated scripts utilizing benefits of OO right deep from dogtail.
* Procedural API: Ace programmer credentials are not necessary to write useful automated scripts with procedural API.
* Easily Extensible: Writing custom classes and helper libraries are easy.
* Results and debug reporting: Separate logs for test case comparisons and debug information are generated.

==Sikuli==
Sikuli automates GUI testing by using image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code.
* Sikuli uses an innovative approach of automating GUI tests by using screenshots and powerpoint slides.
* Sikuli Script is a visual scripting API using [http://en.wikipedia.org/wiki/Jython Jython] to create automation scripts.
* Sikuli includes an integrated development environment (IDE) for writing visual Sikuli scripts with screenshots.

==See Also==
* Web testing tools [http://en.wikipedia.org/wiki/List_of_web_testing_tools]
* Selenium Framework [http://www.mediawiki.org/wiki/Selenium_Framework]
* Selenium [http://www.jroller.com/selenium/]
* Using Selenium [http://aspyct.org/blog/2012/09/09/functional-web-testing-with-selenium-and-ruby/]
* Selenium by example [http://learnseleniumautomation.blogspot.in/2012/08/learn-selenium-webdriver-by-example.html]

==References==
*http://docs.seleniumhq.org/docs/
*http://www.eecs.yorku.ca/course_archive/2004-05/W/4313/Slides/Module10-GUI.pdf
*http://www.cs.helsinki.fi/u/paakki/mikkolainen.pdf
*http://watir.com/
*http://www.gnu.org/software/xnee/
*https://fedorahosted.org/dogtail/
*http://www.cubictest.org/
*http://www.autohotkey.com/
*http://www.sikuli.org/
*http://sivaeluri.blogspot.com/2012/08/advantages-and-disadvantages-of.html
*http://dojotoolkit.org/reference-guide/1.9/util/dohrobot.html
*http://cvs.cs.umd.edu/~atif/papers/MemonIEEEComputer2002.pdf - 2000

==Note to reviewers==
The topic is very vast. Hence the wiki is written based on the guidelines provided by the TA's and the Prof.
* List all GUI tools used in OSS that you can quickly identify.
* Try to describe the tools to the same level of detail, except that you may choose to go into more detail on tools that are used with Rails.
* Listing of commands is not a good idea. You are not writing a reference manual; you are writing a descriptive article that someone might read to learn about what's available before choosing a tool or tools. You should aim for readability.

We have referred the respective tool websites to provide the overview for each one of them. We have provided appropriate citations as well. Additionally the tool and the documentation itself are under GNU/ open source licence and hence will not fall under copyright violation. Please correct us if we are wrong.

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-15T01:59:57Z

Vshesha: /* GUI testing in Ruby and Rails */

==Introduction==
Graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its designed specifications.

GUI testing is difficult mainly due to following reasons :
* Large space of possibilities. Each sequence of GUI commands can result in various states. Evaluation of all these states is essential for validation of the GUI of the given software.
*[http://en.wikipedia.org/wiki/Event-driven_architecture Event-driven architecture]. The test suite has to simulate the various user created actions.

Following are the challenges encountered while testing the graphical user interface of any software or system:
* Automation is difficult.
* The scope for testing is enormous
* Inability to determine the state of the program from GUI.
* [http://en.wikipedia.org/wiki/Regression_testing Regression testing] is difficult. Testcases may not be reusable

The current trend in user interfaces is geared towards graphical user interfaces (GUIs). This presents a problem for designing tests for software, since GUIs are very complex and hence GUI testing is very time consuming. Automation is a requirement for testing any larger graphical user interfaces, but automating GUI tests is not a straightforward task. Techniques which are familiar from the command line interface (CLI) age, don’t translate to the GUI world without problems.

==Test Automation==

The advantages of test automation are as follows.
*Frequent regression testing
*Rapid feedback to developers - The earlier the problems are found, the cheaper it is to fix them. An automated unit test suite finds problems effectively as early as possible, long before the software reaches a customer, and even before it reaches the QA team.
*Virtually unlimited iterations of test case execution
*Support for Agile and extreme development methodologies
*Disciplined documentation of test cases
*Customized defect reporting
*Finding defects missed by manual testing

The challenge is in extending these advantages to GUI testing.

==GUI testing in Ruby and Rails==

Ruby prefers the term scripted testing over the more traditional automated testing. For testing a GUI application there can be several kind of tests in the background to verify the functionality and requirements of an application.

Various frameworks that support testing in Ruby are:
* Test:Unit - It is a unit testing framework for Ruby.
* Capybara[https://github.com/jnicklas/capybara] - It is an integration testing tool for web applications.
* Rspec[http://rspec.info/] - Behaviour Driven Development (BDD) framework/ test tool
* Cucumber[https://github.com/cucumber/cucumber] - It is a tool for running automated acceptance tests written in a behavior-driven development (BDD) style

Ruby on Rails testing frameworks are much more advanced than other web frameworks.

==GUI Testing - Pitfalls==
*Coverage criteria cannot be determined accurately with GUI testing.
*Verifying whether the GUI test executes correctly poses a problem as the logging is difficult.
*Developing a stable regression suite is difficult since simple changes in GUI can render the test suite obsolete.

==GUI Testing Tools==

GUI testing tools serve the purpose of automating the testing process of software with graphical user interfaces. Following are few of the available open source GUI testing tools:

*AutoHotkey
*CubicTest
*Dogtail
*Dojo
*Selenium
*Watir
*GNU Xnee
*Sikuli

==Selenium==

===Introduction===
Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language (Selenium IDE). It also provides a test domain-specific language (Selenese) to write tests in a number of popular programming languages, including Java, C#, [http://groovy.codehaus.org/ Groovy], Perl, PHP, Python and Ruby. The tests can then be run against most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.

===Selenium Tool Suite===
Selenium is composed of multiple software tools.

====Selenium IDE====
*Prototyping tool for building testscripts.
*Firefox plugin provides easy to use interface for developing automated tests.
*Supports 'record and play' feature to create reusable scripts for testing.

====Selenium1====
*Also known as Selenium RC or Remote Control
*Provides flexibility in porting tests across browsers and platforms.
*Currently in maintainence mode. No active development.

====Selenium 2====
*Also known as Selenium Webdriver
*Supports WebDriver API thus providing maximum flexibility in porting the tests.
*Runs Selenium 1’s Selenium RC interface for backwards compatibility.

====Selenium Grid====
*Selenium-Grid allows the Selenium RC solution to scale for large test suites and for test suites that must be run in multiple environments.
*Selenium Grid runs the tests in parallel, that is, different tests can be run at the same time on different remote machines.
*Selenium Grid greatly improves the time it takes to run the suite by making use of parallel processing.

===Supported Browsers and Platforms===

====Selenium 2====
*Google Chrome 12.0.712.0+
*Internet Explorer 6, 7, 8, 9 - 32 and 64-bit where applicable
*Firefox 3.0, 3.5, 3.6, 4.0, 5.0, 6, 7
*Opera 11.5+
*HtmlUnit 2.9
*Android – 2.3+ for phones and tablets (devices & emulators)
*iOS 3+ for phones (devices & emulators) and 3.2+ for tablets (devices & emulators)

====Selenium 1 and Selenium IDE====
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Browser'''
| align="center" style="background:#f0f0f0;"|'''Selenium IDE'''
| align="center" style="background:#f0f0f0;"|'''Selenium 1 (RC)'''
| align="center" style="background:#f0f0f0;"|'''Operating Systems'''
|-
| Firefox 2, 3||Record and playback tests ||Start browser, run tests||Windows, Linux, Mac
|-
| IE 6, 7, 8||Unsupported ||Start browser, run tests||Windows
|-
| Safari 2, 3, 4||Unsupported ||Start browser, run tests||Windows, Mac
|-
| Opera 8, 9, 10||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
| Google Chrome||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
|}

===Advantages===
The chief advantages of Selenium are :
*Flexibility - Test automation can be customized by adding functionality to Selenium test scripts and Selenium framework.
*Open Source - The source code can be downloaded and modified as needed to suit new browsers.
*Deploys on multiple paltforms - Windows, Linux, and Macintosh.

===Disadvantages===
*Identifying the locators and common attributes like id, names etc as well as XPATH, javascript DOM and others is difficult.
*Results are not available in good detail. Debugging failures migt prove to be difficult sometimes.
*Loop and data driven testing is not supported by Selenium IDE.
*Options to verify the images are not available.

==Auto Hot Key==
AutoHotkey automates tests by sending keystrokes and mouse clicks to the target application with the help of a macro recorder.
Virtually any key, button, or combination can become a hotkey.
Following are the notable features of hotkey:
* Expand abbreviations as you type them. For example, typing "gn" can automatically produce "good night".
* Create custom data-entry forms, user interfaces, and menu bars.
* Remap keys and buttons on your keyboard, joystick, and mouse.
* Convert any script into an EXE file that can be run on computers that don't have AutoHotkey installed.

Quick start tutorial : http://www.autohotkey.com/docs/Tutorial.htm

==Watir==
Watir, pronounced water, stands for Web Application Testing in Ruby. Watir is an open-source (BSD) family of Ruby libraries for automating web browsers. It is distributed as a Ruby GEM named 'Watir'. Watir drives browsers the same way people do. It clicks links, fills in forms, presses buttons. Watir also checks results, such as whether expected text appears on the page or not.

There are 2 version available :
* Watir-Classic : supports only Internet Explorer on Windows
* Watir-WebDriver : supports Chrome, Firefox, Internet Explorer, Opera and also running in headless mode (HTMLUnit).

==GNU Xnee==
GNU Xnee is a suite of programs that can record, replay and distribute user actions under the X11 environment. Xnee has the capability to :
* Automate tests like nightly regression
* Demonstrate programs by recording and replaying a user interaction with the system
* Distribute actions from system admin to end users.

The Record and replay ‘macro’ is the highlight of Xnee.

==DOJO==
Dojo is a JavaScript framework targeting the many needs of large-scale client-side web development.

* Dojo abstracts the differences among diverse browsers to provide APIs that will work on all of them (it can even run on the server under Node.js)
* It establishes a framework for defining modules of code and managing their inter-dependencies
* Supports internationalization, localization, and accessibility
* Provides a rich suite of commonly needed utility classes and user-interface widgets.

==CubicTest==
CubicTest is a graphical Eclipse plug-in for writing Selenium and Watir tests. It makes tests faster and easier to write, and provides abstractions to make tests more robust and reusable.

* CubicTest's test editor is centered around pages/states and transitions between these pages/states.
* The model is intuitive for both Ajax and traditional web applications and supports most user interaction types.
* CubicTest features an innovative test recorder and test runner based on Selenium RC which are fully integrated with the graphical test editor.

==Dogtail==
Dogtail is a GUI test tool and automation framework written in Python. It uses Accessibility (a11y) technologies to communicate with desktop applications. Dogtail scripts are written in Python and executed like any other Python program.
Follwoing are the notable features of Dogtail:
* Object-Oriented API: With the object oriented API, you are under control of the UI tree and its elements, allowing you to write sophisticated scripts utilizing benefits of OO right deep from dogtail.
* Procedural API: Ace programmer credentials are not necessary to write useful automated scripts with procedural API.
* Easily Extensible: Writing custom classes and helper libraries are easy.
* Results and debug reporting: Separate logs for test case comparisons and debug information are generated.

==Sikuli==
Sikuli automates GUI testing by using image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code.
* Sikuli uses an innovative approach of automating GUI tests by using screenshots and powerpoint slides.
* Sikuli Script is a visual scripting API using [http://en.wikipedia.org/wiki/Jython Jython] to create automation scripts.
* Sikuli includes an integrated development environment (IDE) for writing visual Sikuli scripts with screenshots.

==See Also==
* Web testing tools [http://en.wikipedia.org/wiki/List_of_web_testing_tools]
* Selenium Framework [http://www.mediawiki.org/wiki/Selenium_Framework]
* Selenium [http://www.jroller.com/selenium/]
* Using Selenium [http://aspyct.org/blog/2012/09/09/functional-web-testing-with-selenium-and-ruby/]
* Selenium by example [http://learnseleniumautomation.blogspot.in/2012/08/learn-selenium-webdriver-by-example.html]

==References==
*http://docs.seleniumhq.org/docs/
*http://www.eecs.yorku.ca/course_archive/2004-05/W/4313/Slides/Module10-GUI.pdf
*http://www.cs.helsinki.fi/u/paakki/mikkolainen.pdf
*http://watir.com/
*http://www.gnu.org/software/xnee/
*https://fedorahosted.org/dogtail/
*http://www.cubictest.org/
*http://www.autohotkey.com/
*http://www.sikuli.org/
*http://sivaeluri.blogspot.com/2012/08/advantages-and-disadvantages-of.html
*http://dojotoolkit.org/reference-guide/1.9/util/dohrobot.html

==Note to reviewers==
The topic is very vast. Hence the wiki is written based on the guidelines provided by the TA's and the Prof.
* List all GUI tools used in OSS that you can quickly identify.
* Try to describe the tools to the same level of detail, except that you may choose to go into more detail on tools that are used with Rails.
* Listing of commands is not a good idea. You are not writing a reference manual; you are writing a descriptive article that someone might read to learn about what's available before choosing a tool or tools. You should aim for readability.

We have referred the respective tool websites to provide the overview for each one of them. We have provided appropriate citations as well. Additionally the tool and the documentation itself are under GNU/ open source licence and hence will not fall under copyright violation. Please correct us if we are wrong.

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-15T01:34:52Z

Vshesha: /* See Also */

==Introduction==
Graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its designed specifications.

GUI testing is difficult mainly due to following reasons :
* Large space of possibilities. Each sequence of GUI commands can result in various states. Evaluation of all these states is essential for validation of the GUI of the given software.
*[http://en.wikipedia.org/wiki/Event-driven_architecture Event-driven architecture]. The test suite has to simulate the various user created actions.

Following are the challenges encountered while testing the graphical user interface of any software or system:
* Automation is difficult.
* The scope for testing is enormous
* Inability to determine the state of the program from GUI.
* [http://en.wikipedia.org/wiki/Regression_testing Regression testing] is difficult. Testcases may not be reusable

The current trend in user interfaces is geared towards graphical user interfaces (GUIs). This presents a problem for designing tests for software, since GUIs are very complex and hence GUI testing is very time consuming. Automation is a requirement for testing any larger graphical user interfaces, but automating GUI tests is not a straightforward task. Techniques which are familiar from the command line interface (CLI) age, don’t translate to the GUI world without problems.

==Test Automation==

The advantages of test automation are as follows.
*Frequent regression testing
*Rapid feedback to developers - The earlier the problems are found, the cheaper it is to fix them. An automated unit test suite finds problems effectively as early as possible, long before the software reaches a customer, and even before it reaches the QA team.
*Virtually unlimited iterations of test case execution
*Support for Agile and extreme development methodologies
*Disciplined documentation of test cases
*Customized defect reporting
*Finding defects missed by manual testing

The challenge is in extending these advantages to GUI testing.

==GUI testing in Ruby and Rails==

Ruby prefers the term scripted testing over the more traditional automated testing. For testing a GUI application there can be several kind of tests in the background to verify the functionality and requirements of an application.

Various frameworks that support testing in Ruby are:
* Test:Unit - It is a unit testing framework for Ruby.
* Capybara - It is an integration testing tool for web applications.
* Rspec - Behaviour Driven Development (BDD) framework/ test tool
* Cucumber - It is a tool for running automated acceptance tests written in a behavior-driven development (BDD) style

Ruby on Rails testing frameworks are much more advanced than other web frameworks.

==GUI Testing Tools==

GUI testing tools serve the purpose of automating the testing process of software with graphical user interfaces. Following are few of the available open source GUI testing tools:

*AutoHotkey
*CubicTest
*Dogtail
*Dojo
*Selenium
*Watir
*GNU Xnee
*Sikuli

==Selenium==

===Introduction===
Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language (Selenium IDE). It also provides a test domain-specific language (Selenese) to write tests in a number of popular programming languages, including Java, C#, [http://groovy.codehaus.org/ Groovy], Perl, PHP, Python and Ruby. The tests can then be run against most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.

===Selenium Tool Suite===
Selenium is composed of multiple software tools.

====Selenium IDE====
*Prototyping tool for building testscripts.
*Firefox plugin provides easy to use interface for developing automated tests.
*Supports 'record and play' feature to create reusable scripts for testing.

====Selenium1====
*Also known as Selenium RC or Remote Control
*Provides flexibility in porting tests across browsers and platforms.
*Currently in maintainence mode. No active development.

====Selenium 2====
*Also known as Selenium Webdriver
*Supports WebDriver API thus providing maximum flexibility in porting the tests.
*Runs Selenium 1’s Selenium RC interface for backwards compatibility.

====Selenium Grid====
*Selenium-Grid allows the Selenium RC solution to scale for large test suites and for test suites that must be run in multiple environments.
*Selenium Grid runs the tests in parallel, that is, different tests can be run at the same time on different remote machines.
*Selenium Grid greatly improves the time it takes to run the suite by making use of parallel processing.

===Supported Browsers and Platforms===

====Selenium 2====
*Google Chrome 12.0.712.0+
*Internet Explorer 6, 7, 8, 9 - 32 and 64-bit where applicable
*Firefox 3.0, 3.5, 3.6, 4.0, 5.0, 6, 7
*Opera 11.5+
*HtmlUnit 2.9
*Android – 2.3+ for phones and tablets (devices & emulators)
*iOS 3+ for phones (devices & emulators) and 3.2+ for tablets (devices & emulators)

====Selenium 1 and Selenium IDE====
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Browser'''
| align="center" style="background:#f0f0f0;"|'''Selenium IDE'''
| align="center" style="background:#f0f0f0;"|'''Selenium 1 (RC)'''
| align="center" style="background:#f0f0f0;"|'''Operating Systems'''
|-
| Firefox 2, 3||Record and playback tests ||Start browser, run tests||Windows, Linux, Mac
|-
| IE 6, 7, 8||Unsupported ||Start browser, run tests||Windows
|-
| Safari 2, 3, 4||Unsupported ||Start browser, run tests||Windows, Mac
|-
| Opera 8, 9, 10||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
| Google Chrome||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
|}

===Advantages===
The chief advantages of Selenium are :
*Flexibility - Test automation can be customized by adding functionality to Selenium test scripts and Selenium framework.
*Open Source - The source code can be downloaded and modified as needed to suit new browsers.
*Deploys on multiple paltforms - Windows, Linux, and Macintosh.

===Disadvantages===
*Identifying the locators and common attributes like id, names etc as well as XPATH, javascript DOM and others is difficult.
*Results are not available in good detail. Debugging failures migt prove to be difficult sometimes.
*Loop and data driven testing is not supported by Selenium IDE.
*Options to verify the images are not available.

==Auto Hot Key==
AutoHotkey automates tests by sending keystrokes and mouse clicks to the target application with the help of a macro recorder.
Virtually any key, button, or combination can become a hotkey.
Following are the notable features of hotkey:
* Expand abbreviations as you type them. For example, typing "gn" can automatically produce "good night".
* Create custom data-entry forms, user interfaces, and menu bars.
* Remap keys and buttons on your keyboard, joystick, and mouse.
* Convert any script into an EXE file that can be run on computers that don't have AutoHotkey installed.

Quick start tutorial : http://www.autohotkey.com/docs/Tutorial.htm

==Watir==
Watir, pronounced water, stands for Web Application Testing in Ruby. Watir is an open-source (BSD) family of Ruby libraries for automating web browsers. It is distributed as a Ruby GEM named 'Watir'. Watir drives browsers the same way people do. It clicks links, fills in forms, presses buttons. Watir also checks results, such as whether expected text appears on the page or not.

There are 2 version available :
* Watir-Classic : supports only Internet Explorer on Windows
* Watir-WebDriver : supports Chrome, Firefox, Internet Explorer, Opera and also running in headless mode (HTMLUnit).

==GNU Xnee==
GNU Xnee is a suite of programs that can record, replay and distribute user actions under the X11 environment. Xnee has the capability to :
* Automate tests like nightly regression
* Demonstrate programs by recording and replaying a user interaction with the system
* Distribute actions from system admin to end users.

The Record and replay ‘macro’ is the highlight of Xnee.

==DOJO==
Dojo is a JavaScript framework targeting the many needs of large-scale client-side web development.

* Dojo abstracts the differences among diverse browsers to provide APIs that will work on all of them (it can even run on the server under Node.js)
* It establishes a framework for defining modules of code and managing their inter-dependencies
* Supports internationalization, localization, and accessibility
* Provides a rich suite of commonly needed utility classes and user-interface widgets.

==CubicTest==
CubicTest is a graphical Eclipse plug-in for writing Selenium and Watir tests. It makes tests faster and easier to write, and provides abstractions to make tests more robust and reusable.

* CubicTest's test editor is centered around pages/states and transitions between these pages/states.
* The model is intuitive for both Ajax and traditional web applications and supports most user interaction types.
* CubicTest features an innovative test recorder and test runner based on Selenium RC which are fully integrated with the graphical test editor.

==Dogtail==
Dogtail is a GUI test tool and automation framework written in Python. It uses Accessibility (a11y) technologies to communicate with desktop applications. Dogtail scripts are written in Python and executed like any other Python program.
Follwoing are the notable features of Dogtail:
* Object-Oriented API: With the object oriented API, you are under control of the UI tree and its elements, allowing you to write sophisticated scripts utilizing benefits of OO right deep from dogtail.
* Procedural API: Ace programmer credentials are not necessary to write useful automated scripts with procedural API.
* Easily Extensible: Writing custom classes and helper libraries are easy.
* Results and debug reporting: Separate logs for test case comparisons and debug information are generated.

==Sikuli==
Sikuli automates GUI testing by using image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code.
* Sikuli uses an innovative approach of automating GUI tests by using screenshots and powerpoint slides.
* Sikuli Script is a visual scripting API using Jython to create automation scripts.
* Sikuli includes an integrated development environment (IDE) for writing visual Sikuli scripts with screenshots.

==See Also==
* Web testing tools [http://en.wikipedia.org/wiki/List_of_web_testing_tools]
* Selenium Framework [http://www.mediawiki.org/wiki/Selenium_Framework]
* Selenium [http://www.jroller.com/selenium/]
* Using Selenium [http://aspyct.org/blog/2012/09/09/functional-web-testing-with-selenium-and-ruby/]
* Selenium by example [http://learnseleniumautomation.blogspot.in/2012/08/learn-selenium-webdriver-by-example.html]

==References==
*http://docs.seleniumhq.org/docs/
*http://www.eecs.yorku.ca/course_archive/2004-05/W/4313/Slides/Module10-GUI.pdf
*http://www.cs.helsinki.fi/u/paakki/mikkolainen.pdf
*http://watir.com/
*http://www.gnu.org/software/xnee/
*https://fedorahosted.org/dogtail/
*http://www.cubictest.org/
*http://www.autohotkey.com/
*http://www.sikuli.org/
*http://sivaeluri.blogspot.com/2012/08/advantages-and-disadvantages-of.html

==Note to reviewers==
The topic is very vast. Hence the wiki is written based on the guidelines provided by the TA's and the Prof.
* List all GUI tools used in OSS that you can quickly identify.
* Try to describe the tools to the same level of detail, except that you may choose to go into more detail on tools that are used with Rails.
* Listing of commands is not a good idea. You are not writing a reference manual; you are writing a descriptive article that someone might read to learn about what's available before choosing a tool or tools. You should aim for readability.

We have referred the respective tool websites to provide the overview for each one of them. We have provided appropriate citations as well. Additionally the tool and the documentation itself are under GNU/ open source licence and hence will not fall under copyright violation. Please correct us if we are wrong.

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-15T01:23:36Z

Vshesha: /* References */

==Introduction==
Graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its designed specifications.

GUI testing is difficult mainly due to following reasons :
* Large space of possibilities. Each sequence of GUI commands can result in various states. Evaluation of all these states is essential for validation of the GUI of the given software.
* Event-driven architecture. The test suite has to simulate the various user created actions.

Following are the challenges encountered while testing the graphical user interface of any software or system:
* Automation is difficult.
* The scope for testing is enormous
* Inability to determine the state of the program from GUI.
* Regression testing is difficult. Testcases may not be reusable

The current trend in user interfaces is geared towards graphical user interfaces (GUIs). This presents a problem for designing tests for software, since GUIs are very complex and hence GUI testing is very time consuming. Automation is a requirement for testing any larger graphical user interfaces, but automating GUI tests isn’t a straightforward task. Techniques which are familiar from the command line interface (CLI) age, don’t translate to the GUI world without problems.

==Test Automation==

The advantages of test automation are as follows.
*Frequent regression testing
*Rapid feedback to developers - The earlier the problems are found, the cheaper it is to fix them. An automated unit test suite finds problems effectively as early as possible, long before the software reaches a customer, and even before it reaches the QA team.
*Virtually unlimited iterations of test case execution
*Support for Agile and extreme development methodologies
*Disciplined documentation of test cases
*Customized defect reporting
*Finding defects missed by manual testing

The challenge is in extending these advantages to GUI testing.

==GUI testing in Ruby and Rails==

Ruby prefers the term scripted testing over the more traditional automated testing. For testing a GUI application there can be several kind of tests in the background to verify the functionality and requirements of an application.

Various frameworks that support testing in Ruby are:
* Test:Unit - It is a unit testing framework for Ruby.
* Capybara - It is an integration testing tool for web applications.
* Rspec - Behaviour Driven Development (BDD) framework/ test tool
* Cucumber - It is a tool for running automated acceptance tests written in a behavior-driven development (BDD) style

Ruby on Rails testing frameworks are much more advanced than other web frameworks.

==GUI Testing Tools==

GUI testing tools serve the purpose of automating the testing process of software with graphical user interfaces. Following are few of the available open source GUI testing tools:

*AutoHotkey
*CubicTest
*Dogtail
*Dojo
*Selenium
*Watir
*GNU Xnee
*Sikuli

==Selenium==

===Introduction===
Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language (Selenium IDE). It also provides a test domain-specific language (Selenese) to write tests in a number of popular programming languages, including Java, C#, [http://groovy.codehaus.org/ Groovy], Perl, PHP, Python and Ruby. The tests can then be run against most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.

===Selenium Tool Suite===
Selenium is composed of multiple software tools.

====Selenium IDE====
*Prototyping tool for building testscripts.
*Firefox plugin provides easy to use interface for developing automated tests.
*Supports 'record and play' feature to create reusable scripts for testing.

====Selenium1====
*Also known as Selenium RC or Remote Control
*Provides flexibility in porting tests across browsers and platforms.
*Currently in maintainence mode. No active development.

====Selenium 2====
*Also known as Selenium Webdriver
*Supports WebDriver API thus providing maximum flexibility in porting the tests.
*Runs Selenium 1’s Selenium RC interface for backwards compatibility.

====Selenium Grid====
*Selenium-Grid allows the Selenium RC solution to scale for large test suites and for test suites that must be run in multiple environments.
*Selenium Grid runs the tests in parallel, that is, different tests can be run at the same time on different remote machines.
*Selenium Grid greatly improves the time it takes to run the suite by making use of parallel processing.

===Supported Browsers and Platforms===

====Selenium 2====
*Google Chrome 12.0.712.0+
*Internet Explorer 6, 7, 8, 9 - 32 and 64-bit where applicable
*Firefox 3.0, 3.5, 3.6, 4.0, 5.0, 6, 7
*Opera 11.5+
*HtmlUnit 2.9
*Android – 2.3+ for phones and tablets (devices & emulators)
*iOS 3+ for phones (devices & emulators) and 3.2+ for tablets (devices & emulators)

====Selenium 1 and Selenium IDE====
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Browser'''
| align="center" style="background:#f0f0f0;"|'''Selenium IDE'''
| align="center" style="background:#f0f0f0;"|'''Selenium 1 (RC)'''
| align="center" style="background:#f0f0f0;"|'''Operating Systems'''
|-
| Firefox 2, 3||Record and playback tests ||Start browser, run tests||Windows, Linux, Mac
|-
| IE 6, 7, 8||Unsupported ||Start browser, run tests||Windows
|-
| Safari 2, 3, 4||Unsupported ||Start browser, run tests||Windows, Mac
|-
| Opera 8, 9, 10||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
| Google Chrome||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
|}

===Advantages===
The chief advantages of Selenium are :
*Flexibility - Test automation can be customized by adding functionality to Selenium test scripts and Selenium framework.
*Open Source - The source code can be downloaded and modified as needed to suit new browsers.
*Deploys on multiple paltforms - Windows, Linux, and Macintosh.

===Disadvantages===
*Identifying the locators and common attributes like id, names etc as well as XPATH, javascript DOM and others is difficult.
*Results are not available in good detail. Debugging failures migt prove to be difficult sometimes.
*Loop and data driven testing is not supported by Selenium IDE.
*Options to verify the images are not available.

==Auto Hot Key==
AutoHotkey automates tests by sending keystrokes and mouse clicks to the target application with the help of a macro recorder.
Virtually any key, button, or combination can become a hotkey.
Following are the notable features of hotkey:
* Expand abbreviations as you type them. For example, typing "gn" can automatically produce "good night".
* Create custom data-entry forms, user interfaces, and menu bars.
* Remap keys and buttons on your keyboard, joystick, and mouse.
* Convert any script into an EXE file that can be run on computers that don't have AutoHotkey installed.

Quick start tutorial : http://www.autohotkey.com/docs/Tutorial.htm

==Watir==
Watir, pronounced water, stands for Web Application Testing in Ruby. Watir is an open-source (BSD) family of Ruby libraries for automating web browsers. It is distributed as a Ruby GEM named 'Watir'. Watir drives browsers the same way people do. It clicks links, fills in forms, presses buttons. Watir also checks results, such as whether expected text appears on the page or not.

There are 2 version available :
* Watir-Classic : supports only Internet Explorer on Windows
* Watir-WebDriver : supports Chrome, Firefox, Internet Explorer, Opera and also running in headless mode (HTMLUnit).

==GNU Xnee==
GNU Xnee is a suite of programs that can record, replay and distribute user actions under the X11 environment. Xnee has the capability to :
* Automate tests like nightly regression
* Demonstrate programs by recording and replaying a user interaction with the system
* Distribute actions from system admin to end users.

The Record and replay ‘macro’ is the highlight of Xnee.

==DOJO==
Dojo is a JavaScript framework targeting the many needs of large-scale client-side web development.

* Dojo abstracts the differences among diverse browsers to provide APIs that will work on all of them (it can even run on the server under Node.js)
* It establishes a framework for defining modules of code and managing their inter-dependencies
* Supports internationalization, localization, and accessibility
* Provides a rich suite of commonly needed utility classes and user-interface widgets.

==CubicTest==
CubicTest is a graphical Eclipse plug-in for writing Selenium and Watir tests. It makes tests faster and easier to write, and provides abstractions to make tests more robust and reusable.

* CubicTest's test editor is centered around pages/states and transitions between these pages/states.
* The model is intuitive for both Ajax and traditional web applications and supports most user interaction types.
* CubicTest features an innovative test recorder and test runner based on Selenium RC which are fully integrated with the graphical test editor.

==Dogtail==
Dogtail is a GUI test tool and automation framework written in Python. It uses Accessibility (a11y) technologies to communicate with desktop applications. Dogtail scripts are written in Python and executed like any other Python program.
Follwoing are the notable features of Dogtail:
* Object-Oriented API: With the object oriented API, you are under control of the UI tree and its elements, allowing you to write sophisticated scripts utilizing benefits of OO right deep from dogtail.
* Procedural API: Ace programmer credentials are not necessary to write useful automated scripts with procedural API.
* Easily Extensible: Writing custom classes and helper libraries are easy.
* Results and debug reporting: Separate logs for test case comparisons and debug information are generated.

==Sikuli==
Sikuli automates GUI testing by using image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code.
* Sikuli uses an innovative approach of automating GUI tests by using screenshots and powerpoint slides.
* Sikuli Script is a visual scripting API using Jython to create automation scripts.
* Sikuli includes an integrated development environment (IDE) for writing visual Sikuli scripts with screenshots.

==See Also==
* Web testing tools [http://en.wikipedia.org/wiki/List_of_web_testing_tools]
* Selenium Framework [http://www.mediawiki.org/wiki/Selenium_Framework]
* Selenium [http://www.jroller.com/selenium/]
* Using Selenium [http://aspyct.org/blog/2012/09/09/functional-web-testing-with-selenium-and-ruby/]

==References==
*http://docs.seleniumhq.org/docs/
*http://www.eecs.yorku.ca/course_archive/2004-05/W/4313/Slides/Module10-GUI.pdf
*http://www.cs.helsinki.fi/u/paakki/mikkolainen.pdf
*http://watir.com/
*http://www.gnu.org/software/xnee/
*https://fedorahosted.org/dogtail/
*http://www.cubictest.org/
*http://www.autohotkey.com/
*http://www.sikuli.org/
*http://sivaeluri.blogspot.com/2012/08/advantages-and-disadvantages-of.html

==Note to reviewers==
The topic is very vast. Hence the wiki is written based on the guidelines provided by the TA's and the Prof.
* List all GUI tools used in OSS that you can quickly identify.
* Try to describe the tools to the same level of detail, except that you may choose to go into more detail on tools that are used with Rails.
* Listing of commands is not a good idea. You are not writing a reference manual; you are writing a descriptive article that someone might read to learn about what's available before choosing a tool or tools. You should aim for readability.

We have referred the respective tool websites to provide the overview for each one of them. We have provided appropriate citations as well. Additionally the tool and the documentation itself are under GNU/ open source licence and hence will not fall under copyright violation. Please correct us if we are wrong.

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-15T01:22:48Z

Vshesha: /* Advantages */

==Introduction==
Graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its designed specifications.

GUI testing is difficult mainly due to following reasons :
* Large space of possibilities. Each sequence of GUI commands can result in various states. Evaluation of all these states is essential for validation of the GUI of the given software.
* Event-driven architecture. The test suite has to simulate the various user created actions.

Following are the challenges encountered while testing the graphical user interface of any software or system:
* Automation is difficult.
* The scope for testing is enormous
* Inability to determine the state of the program from GUI.
* Regression testing is difficult. Testcases may not be reusable

The current trend in user interfaces is geared towards graphical user interfaces (GUIs). This presents a problem for designing tests for software, since GUIs are very complex and hence GUI testing is very time consuming. Automation is a requirement for testing any larger graphical user interfaces, but automating GUI tests isn’t a straightforward task. Techniques which are familiar from the command line interface (CLI) age, don’t translate to the GUI world without problems.

==Test Automation==

The advantages of test automation are as follows.
*Frequent regression testing
*Rapid feedback to developers - The earlier the problems are found, the cheaper it is to fix them. An automated unit test suite finds problems effectively as early as possible, long before the software reaches a customer, and even before it reaches the QA team.
*Virtually unlimited iterations of test case execution
*Support for Agile and extreme development methodologies
*Disciplined documentation of test cases
*Customized defect reporting
*Finding defects missed by manual testing

The challenge is in extending these advantages to GUI testing.

==GUI testing in Ruby and Rails==

Ruby prefers the term scripted testing over the more traditional automated testing. For testing a GUI application there can be several kind of tests in the background to verify the functionality and requirements of an application.

Various frameworks that support testing in Ruby are:
* Test:Unit - It is a unit testing framework for Ruby.
* Capybara - It is an integration testing tool for web applications.
* Rspec - Behaviour Driven Development (BDD) framework/ test tool
* Cucumber - It is a tool for running automated acceptance tests written in a behavior-driven development (BDD) style

Ruby on Rails testing frameworks are much more advanced than other web frameworks.

==GUI Testing Tools==

GUI testing tools serve the purpose of automating the testing process of software with graphical user interfaces. Following are few of the available open source GUI testing tools:

*AutoHotkey
*CubicTest
*Dogtail
*Dojo
*Selenium
*Watir
*GNU Xnee
*Sikuli

==Selenium==

===Introduction===
Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language (Selenium IDE). It also provides a test domain-specific language (Selenese) to write tests in a number of popular programming languages, including Java, C#, [http://groovy.codehaus.org/ Groovy], Perl, PHP, Python and Ruby. The tests can then be run against most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.

===Selenium Tool Suite===
Selenium is composed of multiple software tools.

====Selenium IDE====
*Prototyping tool for building testscripts.
*Firefox plugin provides easy to use interface for developing automated tests.
*Supports 'record and play' feature to create reusable scripts for testing.

====Selenium1====
*Also known as Selenium RC or Remote Control
*Provides flexibility in porting tests across browsers and platforms.
*Currently in maintainence mode. No active development.

====Selenium 2====
*Also known as Selenium Webdriver
*Supports WebDriver API thus providing maximum flexibility in porting the tests.
*Runs Selenium 1’s Selenium RC interface for backwards compatibility.

====Selenium Grid====
*Selenium-Grid allows the Selenium RC solution to scale for large test suites and for test suites that must be run in multiple environments.
*Selenium Grid runs the tests in parallel, that is, different tests can be run at the same time on different remote machines.
*Selenium Grid greatly improves the time it takes to run the suite by making use of parallel processing.

===Supported Browsers and Platforms===

====Selenium 2====
*Google Chrome 12.0.712.0+
*Internet Explorer 6, 7, 8, 9 - 32 and 64-bit where applicable
*Firefox 3.0, 3.5, 3.6, 4.0, 5.0, 6, 7
*Opera 11.5+
*HtmlUnit 2.9
*Android – 2.3+ for phones and tablets (devices & emulators)
*iOS 3+ for phones (devices & emulators) and 3.2+ for tablets (devices & emulators)

====Selenium 1 and Selenium IDE====
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Browser'''
| align="center" style="background:#f0f0f0;"|'''Selenium IDE'''
| align="center" style="background:#f0f0f0;"|'''Selenium 1 (RC)'''
| align="center" style="background:#f0f0f0;"|'''Operating Systems'''
|-
| Firefox 2, 3||Record and playback tests ||Start browser, run tests||Windows, Linux, Mac
|-
| IE 6, 7, 8||Unsupported ||Start browser, run tests||Windows
|-
| Safari 2, 3, 4||Unsupported ||Start browser, run tests||Windows, Mac
|-
| Opera 8, 9, 10||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
| Google Chrome||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
|}

===Advantages===
The chief advantages of Selenium are :
*Flexibility - Test automation can be customized by adding functionality to Selenium test scripts and Selenium framework.
*Open Source - The source code can be downloaded and modified as needed to suit new browsers.
*Deploys on multiple paltforms - Windows, Linux, and Macintosh.

===Disadvantages===
*Identifying the locators and common attributes like id, names etc as well as XPATH, javascript DOM and others is difficult.
*Results are not available in good detail. Debugging failures migt prove to be difficult sometimes.
*Loop and data driven testing is not supported by Selenium IDE.
*Options to verify the images are not available.

==Auto Hot Key==
AutoHotkey automates tests by sending keystrokes and mouse clicks to the target application with the help of a macro recorder.
Virtually any key, button, or combination can become a hotkey.
Following are the notable features of hotkey:
* Expand abbreviations as you type them. For example, typing "gn" can automatically produce "good night".
* Create custom data-entry forms, user interfaces, and menu bars.
* Remap keys and buttons on your keyboard, joystick, and mouse.
* Convert any script into an EXE file that can be run on computers that don't have AutoHotkey installed.

Quick start tutorial : http://www.autohotkey.com/docs/Tutorial.htm

==Watir==
Watir, pronounced water, stands for Web Application Testing in Ruby. Watir is an open-source (BSD) family of Ruby libraries for automating web browsers. It is distributed as a Ruby GEM named 'Watir'. Watir drives browsers the same way people do. It clicks links, fills in forms, presses buttons. Watir also checks results, such as whether expected text appears on the page or not.

There are 2 version available :
* Watir-Classic : supports only Internet Explorer on Windows
* Watir-WebDriver : supports Chrome, Firefox, Internet Explorer, Opera and also running in headless mode (HTMLUnit).

==GNU Xnee==
GNU Xnee is a suite of programs that can record, replay and distribute user actions under the X11 environment. Xnee has the capability to :
* Automate tests like nightly regression
* Demonstrate programs by recording and replaying a user interaction with the system
* Distribute actions from system admin to end users.

The Record and replay ‘macro’ is the highlight of Xnee.

==DOJO==
Dojo is a JavaScript framework targeting the many needs of large-scale client-side web development.

* Dojo abstracts the differences among diverse browsers to provide APIs that will work on all of them (it can even run on the server under Node.js)
* It establishes a framework for defining modules of code and managing their inter-dependencies
* Supports internationalization, localization, and accessibility
* Provides a rich suite of commonly needed utility classes and user-interface widgets.

==CubicTest==
CubicTest is a graphical Eclipse plug-in for writing Selenium and Watir tests. It makes tests faster and easier to write, and provides abstractions to make tests more robust and reusable.

* CubicTest's test editor is centered around pages/states and transitions between these pages/states.
* The model is intuitive for both Ajax and traditional web applications and supports most user interaction types.
* CubicTest features an innovative test recorder and test runner based on Selenium RC which are fully integrated with the graphical test editor.

==Dogtail==
Dogtail is a GUI test tool and automation framework written in Python. It uses Accessibility (a11y) technologies to communicate with desktop applications. Dogtail scripts are written in Python and executed like any other Python program.
Follwoing are the notable features of Dogtail:
* Object-Oriented API: With the object oriented API, you are under control of the UI tree and its elements, allowing you to write sophisticated scripts utilizing benefits of OO right deep from dogtail.
* Procedural API: Ace programmer credentials are not necessary to write useful automated scripts with procedural API.
* Easily Extensible: Writing custom classes and helper libraries are easy.
* Results and debug reporting: Separate logs for test case comparisons and debug information are generated.

==Sikuli==
Sikuli automates GUI testing by using image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code.
* Sikuli uses an innovative approach of automating GUI tests by using screenshots and powerpoint slides.
* Sikuli Script is a visual scripting API using Jython to create automation scripts.
* Sikuli includes an integrated development environment (IDE) for writing visual Sikuli scripts with screenshots.

==See Also==
* Web testing tools [http://en.wikipedia.org/wiki/List_of_web_testing_tools]
* Selenium Framework [http://www.mediawiki.org/wiki/Selenium_Framework]
* Selenium [http://www.jroller.com/selenium/]
* Using Selenium [http://aspyct.org/blog/2012/09/09/functional-web-testing-with-selenium-and-ruby/]

==References==
*http://docs.seleniumhq.org/docs/
*http://www.eecs.yorku.ca/course_archive/2004-05/W/4313/Slides/Module10-GUI.pdf
*http://www.cs.helsinki.fi/u/paakki/mikkolainen.pdf
*http://watir.com/
*http://www.gnu.org/software/xnee/
*https://fedorahosted.org/dogtail/
*http://www.cubictest.org/
*http://www.autohotkey.com/
*http://www.sikuli.org/

==Note to reviewers==
The topic is very vast. Hence the wiki is written based on the guidelines provided by the TA's and the Prof.
* List all GUI tools used in OSS that you can quickly identify.
* Try to describe the tools to the same level of detail, except that you may choose to go into more detail on tools that are used with Rails.
* Listing of commands is not a good idea. You are not writing a reference manual; you are writing a descriptive article that someone might read to learn about what's available before choosing a tool or tools. You should aim for readability.

We have referred the respective tool websites to provide the overview for each one of them. We have provided appropriate citations as well. Additionally the tool and the documentation itself are under GNU/ open source licence and hence will not fall under copyright violation. Please correct us if we are wrong.

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-15T00:46:56Z

Vshesha: /* Introduction */

==Introduction==
Graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its designed specifications.

GUI testing is difficult mainly due to following reasons :
* Large space of possibilities. Each sequence of GUI commands can result in various states. Evaluation of all these states is essential for validation of the GUI of the given software.
* Event-driven architecture. The test suite has to simulate the various user created actions.

Following are the challenges encountered while testing the graphical user interface of any software or system:
* Automation is difficult.
* The scope for testing is enormous
* Inability to determine the state of the program from GUI.
* Regression testing is difficult. Testcases may not be reusable

The current trend in user interfaces is geared towards graphical user interfaces (GUIs). This presents a problem for designing tests for software, since GUIs are very complex and hence GUI testing is very time consuming. Automation is a requirement for testing any larger graphical user interfaces, but automating GUI tests isn’t a straightforward task. Techniques which are familiar from the command line interface (CLI) age, don’t translate to the GUI world without problems.

==Test Automation==

The advantages of test automation are as follows.
*Frequent regression testing
*Rapid feedback to developers - The earlier the problems are found, the cheaper it is to fix them. An automated unit test suite finds problems effectively as early as possible, long before the software reaches a customer, and even before it reaches the QA team.
*Virtually unlimited iterations of test case execution
*Support for Agile and extreme development methodologies
*Disciplined documentation of test cases
*Customized defect reporting
*Finding defects missed by manual testing

The challenge is in extending these advantages to GUI testing.

==GUI testing in Ruby and Rails==

Ruby prefers the term scripted testing over the more traditional automated testing. For testing a GUI application there can be several kind of tests in the background to verify the functionality and requirements of an application.

Various frameworks that support testing in Ruby are:
* Test:Unit - It is a unit testing framework for Ruby.
* Capybara - It is an integration testing tool for web applications.
* Rspec - Behaviour Driven Development (BDD) framework/ test tool
* Cucumber - It is a tool for running automated acceptance tests written in a behavior-driven development (BDD) style

Ruby on Rails testing frameworks are much more advanced than other web frameworks.

==GUI Testing Tools==

GUI testing tools serve the purpose of automating the testing process of software with graphical user interfaces. Following are few of the available open source GUI testing tools:

*AutoHotkey
*CubicTest
*Dogtail
*Dojo
*Selenium
*Watir
*GNU Xnee
*Sikuli

==Selenium==

===Introduction===
Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language (Selenium IDE). It also provides a test domain-specific language (Selenese) to write tests in a number of popular programming languages, including Java, C#, [http://groovy.codehaus.org/ Groovy], Perl, PHP, Python and Ruby. The tests can then be run against most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.

===Selenium Tool Suite===
Selenium is composed of multiple software tools.

====Selenium IDE====
*Prototyping tool for building testscripts.
*Firefox plugin provides easy to use interface for developing automated tests.
*Supports 'record and play' feature to create reusable scripts for testing.

====Selenium1====
*Also known as Selenium RC or Remote Control
*Provides flexibility in porting tests across browsers and platforms.
*Currently in maintainence mode. No active development.

====Selenium 2====
*Also known as Selenium Webdriver
*Supports WebDriver API thus providing maximum flexibility in porting the tests.
*Runs Selenium 1’s Selenium RC interface for backwards compatibility.

====Selenium Grid====
*Selenium-Grid allows the Selenium RC solution to scale for large test suites and for test suites that must be run in multiple environments.
*Selenium Grid runs the tests in parallel, that is, different tests can be run at the same time on different remote machines.
*Selenium Grid greatly improves the time it takes to run the suite by making use of parallel processing.

===Supported Browsers and Platforms===

====Selenium 2====
*Google Chrome 12.0.712.0+
*Internet Explorer 6, 7, 8, 9 - 32 and 64-bit where applicable
*Firefox 3.0, 3.5, 3.6, 4.0, 5.0, 6, 7
*Opera 11.5+
*HtmlUnit 2.9
*Android – 2.3+ for phones and tablets (devices & emulators)
*iOS 3+ for phones (devices & emulators) and 3.2+ for tablets (devices & emulators)

====Selenium 1 and Selenium IDE====
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Browser'''
| align="center" style="background:#f0f0f0;"|'''Selenium IDE'''
| align="center" style="background:#f0f0f0;"|'''Selenium 1 (RC)'''
| align="center" style="background:#f0f0f0;"|'''Operating Systems'''
|-
| Firefox 2, 3||Record and playback tests ||Start browser, run tests||Windows, Linux, Mac
|-
| IE 6, 7, 8||Unsupported ||Start browser, run tests||Windows
|-
| Safari 2, 3, 4||Unsupported ||Start browser, run tests||Windows, Mac
|-
| Opera 8, 9, 10||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
| Google Chrome||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
|}

===Advantages===
The chief advantages of Selenium are :
*Flexibility - Test automation can be customized by adding functionality to Selenium test scripts and Selenium framework.
*Open Source - The source code can be downloaded and modified as needed to suit new browsers.
*Deploys on multiple paltforms - Windows, Linux, and Macintosh.

==Auto Hot Key==
AutoHotkey automates tests by sending keystrokes and mouse clicks to the target application with the help of a macro recorder.
Virtually any key, button, or combination can become a hotkey.
Following are the notable features of hotkey:
* Expand abbreviations as you type them. For example, typing "gn" can automatically produce "good night".
* Create custom data-entry forms, user interfaces, and menu bars.
* Remap keys and buttons on your keyboard, joystick, and mouse.
* Convert any script into an EXE file that can be run on computers that don't have AutoHotkey installed.

Quick start tutorial : http://www.autohotkey.com/docs/Tutorial.htm

==Watir==
Watir, pronounced water, stands for Web Application Testing in Ruby. Watir is an open-source (BSD) family of Ruby libraries for automating web browsers. It is distributed as a Ruby GEM named 'Watir'. Watir drives browsers the same way people do. It clicks links, fills in forms, presses buttons. Watir also checks results, such as whether expected text appears on the page or not.

There are 2 version available :
* Watir-Classic : supports only Internet Explorer on Windows
* Watir-WebDriver : supports Chrome, Firefox, Internet Explorer, Opera and also running in headless mode (HTMLUnit).

==GNU Xnee==
GNU Xnee is a suite of programs that can record, replay and distribute user actions under the X11 environment. Xnee has the capability to :
* Automate tests like nightly regression
* Demonstrate programs by recording and replaying a user interaction with the system
* Distribute actions from system admin to end users.

The Record and replay ‘macro’ is the highlight of Xnee.

==DOJO==
Dojo is a JavaScript framework targeting the many needs of large-scale client-side web development.

* Dojo abstracts the differences among diverse browsers to provide APIs that will work on all of them (it can even run on the server under Node.js)
* It establishes a framework for defining modules of code and managing their inter-dependencies
* Supports internationalization, localization, and accessibility
* Provides a rich suite of commonly needed utility classes and user-interface widgets.

==CubicTest==
CubicTest is a graphical Eclipse plug-in for writing Selenium and Watir tests. It makes tests faster and easier to write, and provides abstractions to make tests more robust and reusable.

* CubicTest's test editor is centered around pages/states and transitions between these pages/states.
* The model is intuitive for both Ajax and traditional web applications and supports most user interaction types.
* CubicTest features an innovative test recorder and test runner based on Selenium RC which are fully integrated with the graphical test editor.

==Dogtail==
Dogtail is a GUI test tool and automation framework written in Python. It uses Accessibility (a11y) technologies to communicate with desktop applications. Dogtail scripts are written in Python and executed like any other Python program.
Follwoing are the notable features of Dogtail:
* Object-Oriented API: With the object oriented API, you are under control of the UI tree and its elements, allowing you to write sophisticated scripts utilizing benefits of OO right deep from dogtail.
* Procedural API: Ace programmer credentials are not necessary to write useful automated scripts with procedural API.
* Easily Extensible: Writing custom classes and helper libraries are easy.
* Results and debug reporting: Separate logs for test case comparisons and debug information are generated.

==Sikuli==
Sikuli automates GUI testing by using image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code.
* Sikuli uses an innovative approach of automating GUI tests by using screenshots and powerpoint slides.
* Sikuli Script is a visual scripting API using Jython to create automation scripts.
* Sikuli includes an integrated development environment (IDE) for writing visual Sikuli scripts with screenshots.

==See Also==
* Web testing tools [http://en.wikipedia.org/wiki/List_of_web_testing_tools]
* Selenium Framework [http://www.mediawiki.org/wiki/Selenium_Framework]
* Selenium [http://www.jroller.com/selenium/]
* Using Selenium [http://aspyct.org/blog/2012/09/09/functional-web-testing-with-selenium-and-ruby/]

==References==
*http://docs.seleniumhq.org/docs/
*http://www.eecs.yorku.ca/course_archive/2004-05/W/4313/Slides/Module10-GUI.pdf
*http://www.cs.helsinki.fi/u/paakki/mikkolainen.pdf
*http://watir.com/
*http://www.gnu.org/software/xnee/
*https://fedorahosted.org/dogtail/
*http://www.cubictest.org/
*http://www.autohotkey.com/
*http://www.sikuli.org/

==Note to reviewers==
The topic is very vast. Hence the wiki is written based on the guidelines provided by the TA's and the Prof.
* List all GUI tools used in OSS that you can quickly identify.
* Try to describe the tools to the same level of detail, except that you may choose to go into more detail on tools that are used with Rails.
* Listing of commands is not a good idea. You are not writing a reference manual; you are writing a descriptive article that someone might read to learn about what's available before choosing a tool or tools. You should aim for readability.

We have referred the respective tool websites to provide the overview for each one of them. We have provided appropriate citations as well. Additionally the tool and the documentation itself are under GNU/ open source licence and hence will not fall under copyright violation. Please correct us if we are wrong.

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-08T01:30:10Z

Vshesha: /* See Also */

==Introduction==
Graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its designed specifications.

GUI testing is difficult mainly due to following reasons :
* Large space of possibilities. Each sequence of GUI commands can result in various states. Evaluation of all these states is essential for validation of the GUI of the given software.
* Event-driven architecture. The test suite has to simulate the various user created actions.

Following are the challenges encountered while testing the graphical user interface of any software or system:
* Automation is difficult.
* The scope for testing is enormous
* Inability to determine the state of the program from GUI.
* Regression testing is difficult. Testcases may not be reusable

The current trend in user interfaces is geared towards graphical user interfaces (GUIs). This presents a problem for designing tests for software, since GUIs are very complex and hence GUI testing is very time consuming. Automation is a requirement for testing any larger graphical user interfaces, but automating GUI tests isn’t a straightforward task. Techniques which are familiar from the command line interface (CLI) age, don’t translate to the GUI world without problems.

==Test Automation==

The advantages of test automation are as follows.
*Frequent regression testing
*Rapid feedback to developers - The earlier the problems are found, the cheaper it is to fix them. An automated unit test suite finds problems effectively as early as possible, long before the software reaches a customer, and even before it reaches the QA team.
*Virtually unlimited iterations of test case execution
*Support for Agile and extreme development methodologies
*Disciplined documentation of test cases
*Customized defect reporting
*Finding defects missed by manual testing

The challenge is in extending these advantages to GUI testing.

==GUI testing in Ruby and Rails==

Ruby prefers the term scripted testing over the more traditional automated testing. For testing a GUI application there can be several kind of tests in the background to verify the functionality and requirements of an application.

Various frameworks that support testing in Ruby are:
* Test:Unit - It is a unit testing framework for Ruby.
* Capybara - It is an integration testing tool for web applications.
* Rspec - Behaviour Driven Development (BDD) framework/ test tool
* Cucumber - It is a tool for running automated acceptance tests written in a behavior-driven development (BDD) style

Ruby on Rails testing frameworks are much more advanced than other web frameworks.

==GUI Testing Tools==

GUI testing tools serve the purpose of automating the testing process of software with graphical user interfaces. Following are few of the available open source GUI testing tools:

*AutoHotkey
*CubicTest
*Dogtail
*Dojo
*Selenium
*Watir
*GNU Xnee
*Sikuli

==Selenium==

===Introduction===
Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language (Selenium IDE). It also provides a test domain-specific language (Selenese) to write tests in a number of popular programming languages, including Java, C#, Groovy, Perl, PHP, Python and Ruby. The tests can then be run against most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.

===Selenium Tool Suite===
Selenium is composed of multiple software tools.

====Selenium IDE====
*Prototyping tool for building testscripts.
*Firefox plugin provides easy to use interface for developing automated tests.
*Supports 'record and play' feature to create reusable scripts for testing.

====Selenium1====
*Also known as Selenium RC or Remote Control
*Provides flexibility in porting tests across browsers and platforms.
*Currently in maintainence mode. No active development.

====Selenium 2====
*Also known as Selenium Webdriver
*Supports WebDriver API thus providing maximum flexibility in porting the tests.
*Runs Selenium 1’s Selenium RC interface for backwards compatibility.

====Selenium Grid====
*Selenium-Grid allows the Selenium RC solution to scale for large test suites and for test suites that must be run in multiple environments.
*Selenium Grid runs the tests in parallel, that is, different tests can be run at the same time on different remote machines.
*Selenium Grid greatly improves the time it takes to run the suite by making use of parallel processing.

===Supported Browsers and Platforms===

====Selenium 2====
*Google Chrome 12.0.712.0+
*Internet Explorer 6, 7, 8, 9 - 32 and 64-bit where applicable
*Firefox 3.0, 3.5, 3.6, 4.0, 5.0, 6, 7
*Opera 11.5+
*HtmlUnit 2.9
*Android – 2.3+ for phones and tablets (devices & emulators)
*iOS 3+ for phones (devices & emulators) and 3.2+ for tablets (devices & emulators)

====Selenium 1 and Selenium IDE====
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Browser'''
| align="center" style="background:#f0f0f0;"|'''Selenium IDE'''
| align="center" style="background:#f0f0f0;"|'''Selenium 1 (RC)'''
| align="center" style="background:#f0f0f0;"|'''Operating Systems'''
|-
| Firefox 2, 3||Record and playback tests ||Start browser, run tests||Windows, Linux, Mac
|-
| IE 6, 7, 8||Unsupported ||Start browser, run tests||Windows
|-
| Safari 2, 3, 4||Unsupported ||Start browser, run tests||Windows, Mac
|-
| Opera 8, 9, 10||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
| Google Chrome||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
|}

===Advantages===
The chief advantages of Selenium are :
*Flexibility - Test automation can be customized by adding functionality to Selenium test scripts and Selenium framework.
*Open Source - The source code can be downloaded and modified as needed to suit new browsers.
*Deploys on multiple paltforms - Windows, Linux, and Macintosh.

==Auto Hot Key==
AutoHotkey automates tests by sending keystrokes and mouse clicks to the target application with the help of a macro recorder.
Virtually any key, button, or combination can become a hotkey.
Following are the notable features of hotkey:
* Expand abbreviations as you type them. For example, typing "gn" can automatically produce "good night".
* Create custom data-entry forms, user interfaces, and menu bars.
* Remap keys and buttons on your keyboard, joystick, and mouse.
* Convert any script into an EXE file that can be run on computers that don't have AutoHotkey installed.

Quick start tutorial : http://www.autohotkey.com/docs/Tutorial.htm

==Watir==
Watir, pronounced water, stands for Web Application Testing in Ruby. Watir is an open-source (BSD) family of Ruby libraries for automating web browsers. It is distributed as a Ruby GEM named 'Watir'. Watir drives browsers the same way people do. It clicks links, fills in forms, presses buttons. Watir also checks results, such as whether expected text appears on the page or not.

There are 2 version available :
* Watir-Classic : supports only Internet Explorer on Windows
* Watir-WebDriver : supports Chrome, Firefox, Internet Explorer, Opera and also running in headless mode (HTMLUnit).

==GNU Xnee==
GNU Xnee is a suite of programs that can record, replay and distribute user actions under the X11 environment. Xnee has the capability to :
* Automate tests like nightly regression
* Demonstrate programs by recording and replaying a user interaction with the system
* Distribute actions from system admin to end users.

The Record and replay ‘macro’ is the highlight of Xnee.

==DOJO==
Dojo is a JavaScript framework targeting the many needs of large-scale client-side web development.

* Dojo abstracts the differences among diverse browsers to provide APIs that will work on all of them (it can even run on the server under Node.js)
* It establishes a framework for defining modules of code and managing their inter-dependencies
* Supports internationalization, localization, and accessibility
* Provides a rich suite of commonly needed utility classes and user-interface widgets.

==CubicTest==
CubicTest is a graphical Eclipse plug-in for writing Selenium and Watir tests. It makes tests faster and easier to write, and provides abstractions to make tests more robust and reusable.

* CubicTest's test editor is centered around pages/states and transitions between these pages/states.
* The model is intuitive for both Ajax and traditional web applications and supports most user interaction types.
* CubicTest features an innovative test recorder and test runner based on Selenium RC which are fully integrated with the graphical test editor.

==Dogtail==
Dogtail is a GUI test tool and automation framework written in Python. It uses Accessibility (a11y) technologies to communicate with desktop applications. Dogtail scripts are written in Python and executed like any other Python program.
Follwoing are the notable features of Dogtail:
* Object-Oriented API: With the object oriented API, you are under control of the UI tree and its elements, allowing you to write sophisticated scripts utilizing benefits of OO right deep from dogtail.
* Procedural API: Ace programmer credentials are not necessary to write useful automated scripts with procedural API.
* Easily Extensible: Writing custom classes and helper libraries are easy.
* Results and debug reporting: Separate logs for test case comparisons and debug information are generated.

==Sikuli==
Sikuli automates GUI testing by using image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code.
* Sikuli uses an innovative approach of automating GUI tests by using screenshots and powerpoint slides.
* Sikuli Script is a visual scripting API using Jython to create automation scripts.
* Sikuli includes an integrated development environment (IDE) for writing visual Sikuli scripts with screenshots.

==See Also==
* Web testing tools [http://en.wikipedia.org/wiki/List_of_web_testing_tools]
* Selenium Framework [http://www.mediawiki.org/wiki/Selenium_Framework]
* Selenium [http://www.jroller.com/selenium/]
* Using Selenium [http://aspyct.org/blog/2012/09/09/functional-web-testing-with-selenium-and-ruby/]

==References==
*http://docs.seleniumhq.org/docs/
*http://www.eecs.yorku.ca/course_archive/2004-05/W/4313/Slides/Module10-GUI.pdf
*http://www.cs.helsinki.fi/u/paakki/mikkolainen.pdf
*http://watir.com/
*http://www.gnu.org/software/xnee/
*https://fedorahosted.org/dogtail/
*http://www.cubictest.org/
*http://www.autohotkey.com/
*http://www.sikuli.org/

==Note to reviewers==
The topic is very vast. Hence the wiki is written based on the guidelines provided by the TA's and the Prof.
* List all GUI tools used in OSS that you can quickly identify.
* Try to describe the tools to the same level of detail, except that you may choose to go into more detail on tools that are used with Rails.
* Listing of commands is not a good idea. You are not writing a reference manual; you are writing a descriptive article that someone might read to learn about what's available before choosing a tool or tools. You should aim for readability.

We have referred the respective tool websites to provide the overview for each one of them. We have provided appropriate citations as well. Additionally the tool and the documentation itself are under GNU/ open source licence and hence will not fall under copyright violation. Please correct us if we are wrong.

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-08T01:29:43Z

Vshesha: /* Advantage */

==Introduction==
Graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its designed specifications.

GUI testing is difficult mainly due to following reasons :
* Large space of possibilities. Each sequence of GUI commands can result in various states. Evaluation of all these states is essential for validation of the GUI of the given software.
* Event-driven architecture. The test suite has to simulate the various user created actions.

Following are the challenges encountered while testing the graphical user interface of any software or system:
* Automation is difficult.
* The scope for testing is enormous
* Inability to determine the state of the program from GUI.
* Regression testing is difficult. Testcases may not be reusable

The current trend in user interfaces is geared towards graphical user interfaces (GUIs). This presents a problem for designing tests for software, since GUIs are very complex and hence GUI testing is very time consuming. Automation is a requirement for testing any larger graphical user interfaces, but automating GUI tests isn’t a straightforward task. Techniques which are familiar from the command line interface (CLI) age, don’t translate to the GUI world without problems.

==Test Automation==

The advantages of test automation are as follows.
*Frequent regression testing
*Rapid feedback to developers - The earlier the problems are found, the cheaper it is to fix them. An automated unit test suite finds problems effectively as early as possible, long before the software reaches a customer, and even before it reaches the QA team.
*Virtually unlimited iterations of test case execution
*Support for Agile and extreme development methodologies
*Disciplined documentation of test cases
*Customized defect reporting
*Finding defects missed by manual testing

The challenge is in extending these advantages to GUI testing.

==GUI testing in Ruby and Rails==

Ruby prefers the term scripted testing over the more traditional automated testing. For testing a GUI application there can be several kind of tests in the background to verify the functionality and requirements of an application.

Various frameworks that support testing in Ruby are:
* Test:Unit - It is a unit testing framework for Ruby.
* Capybara - It is an integration testing tool for web applications.
* Rspec - Behaviour Driven Development (BDD) framework/ test tool
* Cucumber - It is a tool for running automated acceptance tests written in a behavior-driven development (BDD) style

Ruby on Rails testing frameworks are much more advanced than other web frameworks.

==GUI Testing Tools==

GUI testing tools serve the purpose of automating the testing process of software with graphical user interfaces. Following are few of the available open source GUI testing tools:

*AutoHotkey
*CubicTest
*Dogtail
*Dojo
*Selenium
*Watir
*GNU Xnee
*Sikuli

==Selenium==

===Introduction===
Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language (Selenium IDE). It also provides a test domain-specific language (Selenese) to write tests in a number of popular programming languages, including Java, C#, Groovy, Perl, PHP, Python and Ruby. The tests can then be run against most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.

===Selenium Tool Suite===
Selenium is composed of multiple software tools.

====Selenium IDE====
*Prototyping tool for building testscripts.
*Firefox plugin provides easy to use interface for developing automated tests.
*Supports 'record and play' feature to create reusable scripts for testing.

====Selenium1====
*Also known as Selenium RC or Remote Control
*Provides flexibility in porting tests across browsers and platforms.
*Currently in maintainence mode. No active development.

====Selenium 2====
*Also known as Selenium Webdriver
*Supports WebDriver API thus providing maximum flexibility in porting the tests.
*Runs Selenium 1’s Selenium RC interface for backwards compatibility.

====Selenium Grid====
*Selenium-Grid allows the Selenium RC solution to scale for large test suites and for test suites that must be run in multiple environments.
*Selenium Grid runs the tests in parallel, that is, different tests can be run at the same time on different remote machines.
*Selenium Grid greatly improves the time it takes to run the suite by making use of parallel processing.

===Supported Browsers and Platforms===

====Selenium 2====
*Google Chrome 12.0.712.0+
*Internet Explorer 6, 7, 8, 9 - 32 and 64-bit where applicable
*Firefox 3.0, 3.5, 3.6, 4.0, 5.0, 6, 7
*Opera 11.5+
*HtmlUnit 2.9
*Android – 2.3+ for phones and tablets (devices & emulators)
*iOS 3+ for phones (devices & emulators) and 3.2+ for tablets (devices & emulators)

====Selenium 1 and Selenium IDE====
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Browser'''
| align="center" style="background:#f0f0f0;"|'''Selenium IDE'''
| align="center" style="background:#f0f0f0;"|'''Selenium 1 (RC)'''
| align="center" style="background:#f0f0f0;"|'''Operating Systems'''
|-
| Firefox 2, 3||Record and playback tests ||Start browser, run tests||Windows, Linux, Mac
|-
| IE 6, 7, 8||Unsupported ||Start browser, run tests||Windows
|-
| Safari 2, 3, 4||Unsupported ||Start browser, run tests||Windows, Mac
|-
| Opera 8, 9, 10||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
| Google Chrome||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
|}

===Advantages===
The chief advantages of Selenium are :
*Flexibility - Test automation can be customized by adding functionality to Selenium test scripts and Selenium framework.
*Open Source - The source code can be downloaded and modified as needed to suit new browsers.
*Deploys on multiple paltforms - Windows, Linux, and Macintosh.

==Auto Hot Key==
AutoHotkey automates tests by sending keystrokes and mouse clicks to the target application with the help of a macro recorder.
Virtually any key, button, or combination can become a hotkey.
Following are the notable features of hotkey:
* Expand abbreviations as you type them. For example, typing "gn" can automatically produce "good night".
* Create custom data-entry forms, user interfaces, and menu bars.
* Remap keys and buttons on your keyboard, joystick, and mouse.
* Convert any script into an EXE file that can be run on computers that don't have AutoHotkey installed.

Quick start tutorial : http://www.autohotkey.com/docs/Tutorial.htm

==Watir==
Watir, pronounced water, stands for Web Application Testing in Ruby. Watir is an open-source (BSD) family of Ruby libraries for automating web browsers. It is distributed as a Ruby GEM named 'Watir'. Watir drives browsers the same way people do. It clicks links, fills in forms, presses buttons. Watir also checks results, such as whether expected text appears on the page or not.

There are 2 version available :
* Watir-Classic : supports only Internet Explorer on Windows
* Watir-WebDriver : supports Chrome, Firefox, Internet Explorer, Opera and also running in headless mode (HTMLUnit).

==GNU Xnee==
GNU Xnee is a suite of programs that can record, replay and distribute user actions under the X11 environment. Xnee has the capability to :
* Automate tests like nightly regression
* Demonstrate programs by recording and replaying a user interaction with the system
* Distribute actions from system admin to end users.

The Record and replay ‘macro’ is the highlight of Xnee.

==DOJO==
Dojo is a JavaScript framework targeting the many needs of large-scale client-side web development.

* Dojo abstracts the differences among diverse browsers to provide APIs that will work on all of them (it can even run on the server under Node.js)
* It establishes a framework for defining modules of code and managing their inter-dependencies
* Supports internationalization, localization, and accessibility
* Provides a rich suite of commonly needed utility classes and user-interface widgets.

==CubicTest==
CubicTest is a graphical Eclipse plug-in for writing Selenium and Watir tests. It makes tests faster and easier to write, and provides abstractions to make tests more robust and reusable.

* CubicTest's test editor is centered around pages/states and transitions between these pages/states.
* The model is intuitive for both Ajax and traditional web applications and supports most user interaction types.
* CubicTest features an innovative test recorder and test runner based on Selenium RC which are fully integrated with the graphical test editor.

==Dogtail==
Dogtail is a GUI test tool and automation framework written in Python. It uses Accessibility (a11y) technologies to communicate with desktop applications. Dogtail scripts are written in Python and executed like any other Python program.
Follwoing are the notable features of Dogtail:
* Object-Oriented API: With the object oriented API, you are under control of the UI tree and its elements, allowing you to write sophisticated scripts utilizing benefits of OO right deep from dogtail.
* Procedural API: Ace programmer credentials are not necessary to write useful automated scripts with procedural API.
* Easily Extensible: Writing custom classes and helper libraries are easy.
* Results and debug reporting: Separate logs for test case comparisons and debug information are generated.

==Sikuli==
Sikuli automates GUI testing by using image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code.
* Sikuli uses an innovative approach of automating GUI tests by using screenshots and powerpoint slides.
* Sikuli Script is a visual scripting API using Jython to create automation scripts.
* Sikuli includes an integrated development environment (IDE) for writing visual Sikuli scripts with screenshots.

==See Also==
* Web testing tools [http://en.wikipedia.org/wiki/List_of_web_testing_tools]
* Selenium Framework [http://www.mediawiki.org/wiki/Selenium_Framework]
* Selenium [http://www.jroller.com/selenium/]

==References==
*http://docs.seleniumhq.org/docs/
*http://www.eecs.yorku.ca/course_archive/2004-05/W/4313/Slides/Module10-GUI.pdf
*http://www.cs.helsinki.fi/u/paakki/mikkolainen.pdf
*http://watir.com/
*http://www.gnu.org/software/xnee/
*https://fedorahosted.org/dogtail/
*http://www.cubictest.org/
*http://www.autohotkey.com/
*http://www.sikuli.org/

==Note to reviewers==
The topic is very vast. Hence the wiki is written based on the guidelines provided by the TA's and the Prof.
* List all GUI tools used in OSS that you can quickly identify.
* Try to describe the tools to the same level of detail, except that you may choose to go into more detail on tools that are used with Rails.
* Listing of commands is not a good idea. You are not writing a reference manual; you are writing a descriptive article that someone might read to learn about what's available before choosing a tool or tools. You should aim for readability.

We have referred the respective tool websites to provide the overview for each one of them. We have provided appropriate citations as well. Additionally the tool and the documentation itself are under GNU/ open source licence and hence will not fall under copyright violation. Please correct us if we are wrong.

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-08T01:28:31Z

Vshesha: /* Test Automation */

==Introduction==
Graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its designed specifications.

GUI testing is difficult mainly due to following reasons :
* Large space of possibilities. Each sequence of GUI commands can result in various states. Evaluation of all these states is essential for validation of the GUI of the given software.
* Event-driven architecture. The test suite has to simulate the various user created actions.

Following are the challenges encountered while testing the graphical user interface of any software or system:
* Automation is difficult.
* The scope for testing is enormous
* Inability to determine the state of the program from GUI.
* Regression testing is difficult. Testcases may not be reusable

The current trend in user interfaces is geared towards graphical user interfaces (GUIs). This presents a problem for designing tests for software, since GUIs are very complex and hence GUI testing is very time consuming. Automation is a requirement for testing any larger graphical user interfaces, but automating GUI tests isn’t a straightforward task. Techniques which are familiar from the command line interface (CLI) age, don’t translate to the GUI world without problems.

==Test Automation==

The advantages of test automation are as follows.
*Frequent regression testing
*Rapid feedback to developers - The earlier the problems are found, the cheaper it is to fix them. An automated unit test suite finds problems effectively as early as possible, long before the software reaches a customer, and even before it reaches the QA team.
*Virtually unlimited iterations of test case execution
*Support for Agile and extreme development methodologies
*Disciplined documentation of test cases
*Customized defect reporting
*Finding defects missed by manual testing

The challenge is in extending these advantages to GUI testing.

==GUI testing in Ruby and Rails==

Ruby prefers the term scripted testing over the more traditional automated testing. For testing a GUI application there can be several kind of tests in the background to verify the functionality and requirements of an application.

Various frameworks that support testing in Ruby are:
* Test:Unit - It is a unit testing framework for Ruby.
* Capybara - It is an integration testing tool for web applications.
* Rspec - Behaviour Driven Development (BDD) framework/ test tool
* Cucumber - It is a tool for running automated acceptance tests written in a behavior-driven development (BDD) style

Ruby on Rails testing frameworks are much more advanced than other web frameworks.

==GUI Testing Tools==

GUI testing tools serve the purpose of automating the testing process of software with graphical user interfaces. Following are few of the available open source GUI testing tools:

*AutoHotkey
*CubicTest
*Dogtail
*Dojo
*Selenium
*Watir
*GNU Xnee
*Sikuli

==Selenium==

===Introduction===
Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language (Selenium IDE). It also provides a test domain-specific language (Selenese) to write tests in a number of popular programming languages, including Java, C#, Groovy, Perl, PHP, Python and Ruby. The tests can then be run against most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.

===Selenium Tool Suite===
Selenium is composed of multiple software tools.

====Selenium IDE====
*Prototyping tool for building testscripts.
*Firefox plugin provides easy to use interface for developing automated tests.
*Supports 'record and play' feature to create reusable scripts for testing.

====Selenium1====
*Also known as Selenium RC or Remote Control
*Provides flexibility in porting tests across browsers and platforms.
*Currently in maintainence mode. No active development.

====Selenium 2====
*Also known as Selenium Webdriver
*Supports WebDriver API thus providing maximum flexibility in porting the tests.
*Runs Selenium 1’s Selenium RC interface for backwards compatibility.

====Selenium Grid====
*Selenium-Grid allows the Selenium RC solution to scale for large test suites and for test suites that must be run in multiple environments.
*Selenium Grid runs the tests in parallel, that is, different tests can be run at the same time on different remote machines.
*Selenium Grid greatly improves the time it takes to run the suite by making use of parallel processing.

===Supported Browsers and Platforms===

====Selenium 2====
*Google Chrome 12.0.712.0+
*Internet Explorer 6, 7, 8, 9 - 32 and 64-bit where applicable
*Firefox 3.0, 3.5, 3.6, 4.0, 5.0, 6, 7
*Opera 11.5+
*HtmlUnit 2.9
*Android – 2.3+ for phones and tablets (devices & emulators)
*iOS 3+ for phones (devices & emulators) and 3.2+ for tablets (devices & emulators)

====Selenium 1 and Selenium IDE====
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Browser'''
| align="center" style="background:#f0f0f0;"|'''Selenium IDE'''
| align="center" style="background:#f0f0f0;"|'''Selenium 1 (RC)'''
| align="center" style="background:#f0f0f0;"|'''Operating Systems'''
|-
| Firefox 2, 3||Record and playback tests ||Start browser, run tests||Windows, Linux, Mac
|-
| IE 6, 7, 8||Unsupported ||Start browser, run tests||Windows
|-
| Safari 2, 3, 4||Unsupported ||Start browser, run tests||Windows, Mac
|-
| Opera 8, 9, 10||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
| Google Chrome||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
|}

===Advantage===
The chief advantages of Selenium are :
*Flexibility - Test automation can be customized by adding functionality to Selenium test scripts and Selenium framework.
*Open Source - The source code can be downloaded and modified as needed to suit new browsers.
*Deploys on multiple paltforms - Windows, Linux, and Macintosh.

More here

NOte ; can we add this http://aspyct.org/blog/2012/09/09/functional-web-testing-with-selenium-and-ruby/

==Auto Hot Key==
AutoHotkey automates tests by sending keystrokes and mouse clicks to the target application with the help of a macro recorder.
Virtually any key, button, or combination can become a hotkey.
Following are the notable features of hotkey:
* Expand abbreviations as you type them. For example, typing "gn" can automatically produce "good night".
* Create custom data-entry forms, user interfaces, and menu bars.
* Remap keys and buttons on your keyboard, joystick, and mouse.
* Convert any script into an EXE file that can be run on computers that don't have AutoHotkey installed.

Quick start tutorial : http://www.autohotkey.com/docs/Tutorial.htm

==Watir==
Watir, pronounced water, stands for Web Application Testing in Ruby. Watir is an open-source (BSD) family of Ruby libraries for automating web browsers. It is distributed as a Ruby GEM named 'Watir'. Watir drives browsers the same way people do. It clicks links, fills in forms, presses buttons. Watir also checks results, such as whether expected text appears on the page or not.

There are 2 version available :
* Watir-Classic : supports only Internet Explorer on Windows
* Watir-WebDriver : supports Chrome, Firefox, Internet Explorer, Opera and also running in headless mode (HTMLUnit).

==GNU Xnee==
GNU Xnee is a suite of programs that can record, replay and distribute user actions under the X11 environment. Xnee has the capability to :
* Automate tests like nightly regression
* Demonstrate programs by recording and replaying a user interaction with the system
* Distribute actions from system admin to end users.

The Record and replay ‘macro’ is the highlight of Xnee.

==DOJO==
Dojo is a JavaScript framework targeting the many needs of large-scale client-side web development.

* Dojo abstracts the differences among diverse browsers to provide APIs that will work on all of them (it can even run on the server under Node.js)
* It establishes a framework for defining modules of code and managing their inter-dependencies
* Supports internationalization, localization, and accessibility
* Provides a rich suite of commonly needed utility classes and user-interface widgets.

==CubicTest==
CubicTest is a graphical Eclipse plug-in for writing Selenium and Watir tests. It makes tests faster and easier to write, and provides abstractions to make tests more robust and reusable.

* CubicTest's test editor is centered around pages/states and transitions between these pages/states.
* The model is intuitive for both Ajax and traditional web applications and supports most user interaction types.
* CubicTest features an innovative test recorder and test runner based on Selenium RC which are fully integrated with the graphical test editor.

==Dogtail==
Dogtail is a GUI test tool and automation framework written in Python. It uses Accessibility (a11y) technologies to communicate with desktop applications. Dogtail scripts are written in Python and executed like any other Python program.
Follwoing are the notable features of Dogtail:
* Object-Oriented API: With the object oriented API, you are under control of the UI tree and its elements, allowing you to write sophisticated scripts utilizing benefits of OO right deep from dogtail.
* Procedural API: Ace programmer credentials are not necessary to write useful automated scripts with procedural API.
* Easily Extensible: Writing custom classes and helper libraries are easy.
* Results and debug reporting: Separate logs for test case comparisons and debug information are generated.

==Sikuli==
Sikuli automates GUI testing by using image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code.
* Sikuli uses an innovative approach of automating GUI tests by using screenshots and powerpoint slides.
* Sikuli Script is a visual scripting API using Jython to create automation scripts.
* Sikuli includes an integrated development environment (IDE) for writing visual Sikuli scripts with screenshots.

==See Also==
* Web testing tools [http://en.wikipedia.org/wiki/List_of_web_testing_tools]
* Selenium Framework [http://www.mediawiki.org/wiki/Selenium_Framework]
* Selenium [http://www.jroller.com/selenium/]

==References==
*http://docs.seleniumhq.org/docs/
*http://www.eecs.yorku.ca/course_archive/2004-05/W/4313/Slides/Module10-GUI.pdf
*http://www.cs.helsinki.fi/u/paakki/mikkolainen.pdf
*http://watir.com/
*http://www.gnu.org/software/xnee/
*https://fedorahosted.org/dogtail/
*http://www.cubictest.org/
*http://www.autohotkey.com/
*http://www.sikuli.org/

==Note to reviewers==
The topic is very vast. Hence the wiki is written based on the guidelines provided by the TA's and the Prof.
* List all GUI tools used in OSS that you can quickly identify.
* Try to describe the tools to the same level of detail, except that you may choose to go into more detail on tools that are used with Rails.
* Listing of commands is not a good idea. You are not writing a reference manual; you are writing a descriptive article that someone might read to learn about what's available before choosing a tool or tools. You should aim for readability.

We have referred the respective tool websites to provide the overview for each one of them. We have provided appropriate citations as well. Additionally the tool and the documentation itself are under GNU/ open source licence and hence will not fall under copyright violation. Please correct us if we are wrong.

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-07T23:47:11Z

Vshesha: /* See Also */

==Introduction==
Graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its designed specifications.

GUI testing is difficult mainly due to following reasons :
* Large space of possibilities. Each sequence of GUI commands can result in various states. Evaluation of all these states is essential for validation of the GUI of the given software.
* Event-driven architecture. The test suite has to simulate the various user created actions.

Following are the challenges encountered while testing the graphical user interface of any software or system:
* Automation is difficult.
* The scope for testing is enormous
* Inability to determine the state of the program from GUI.
* Regression testing is difficult. Testcases may not be reusable

The current trend in user interfaces is geared towards graphical user interfaces (GUIs). This presents a problem for designing tests for software, since GUIs are very complex and hence GUI testing is very time consuming. Automation is a requirement for testing any larger graphical user interfaces, but automating GUI tests isn’t a straightforward task. Techniques which are familiar from the command line interface (CLI) age, don’t translate to the GUI world without problems.

==Test Automation==

Note : Rework

The advantages of test automation are as follows.
*Frequent regression testing
*Rapid feedback to developers - The earlier the problems are found, the cheaper it is to fix them. An automated unit test suite finds problems effectively as early as possible, long before the software reaches a customer, and even before it reaches the QA team.
*Virtually unlimited iterations of test case execution
*Support for Agile and extreme development methodologies
*Disciplined documentation of test cases
*Customized defect reporting
*Finding defects missed by manual testing

The challenge is in extending these advantages to GUI testing.

==GUI testing in Ruby and Rails==

Ruby prefers the term scripted testing over the more traditional automated testing. For testing a GUI application there can be several kind of tests in the background to verify the functionality and requirements of an application.

Various frameworks that support testing in Ruby are:
* Test:Unit - It is a unit testing framework for Ruby.
* Capybara - It is an integration testing tool for web applications.
* Rspec - Behaviour Driven Development (BDD) framework/ test tool
* Cucumber - It is a tool for running automated acceptance tests written in a behavior-driven development (BDD) style

Ruby on Rails testing frameworks are much more advanced than other web frameworks.

==GUI Testing Tools==

GUI testing tools serve the purpose of automating the testing process of software with graphical user interfaces. Following are few of the available open source GUI testing tools:

*AutoHotkey
*CubicTest
*Dogtail
*Dojo
*Selenium
*Watir
*GNU Xnee
*Sikuli

==Selenium==

===Introduction===
Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language (Selenium IDE). It also provides a test domain-specific language (Selenese) to write tests in a number of popular programming languages, including Java, C#, Groovy, Perl, PHP, Python and Ruby. The tests can then be run against most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.

===Selenium Tool Suite===
Selenium is composed of multiple software tools.

====Selenium IDE====
*Prototyping tool for building testscripts.
*Firefox plugin provides easy to use interface for developing automated tests.
*Supports 'record and play' feature to create reusable scripts for testing.

====Selenium1====
*Also known as Selenium RC or Remote Control
*Provides flexibility in porting tests across browsers and platforms.
*Currently in maintainence mode. No active development.

====Selenium 2====
*Also known as Selenium Webdriver
*Supports WebDriver API thus providing maximum flexibility in porting the tests.
*Runs Selenium 1’s Selenium RC interface for backwards compatibility.

====Selenium Grid====
*Selenium-Grid allows the Selenium RC solution to scale for large test suites and for test suites that must be run in multiple environments.
*Selenium Grid runs the tests in parallel, that is, different tests can be run at the same time on different remote machines.
*Selenium Grid greatly improves the time it takes to run the suite by making use of parallel processing.

===Supported Browsers and Platforms===

====Selenium 2====
*Google Chrome 12.0.712.0+
*Internet Explorer 6, 7, 8, 9 - 32 and 64-bit where applicable
*Firefox 3.0, 3.5, 3.6, 4.0, 5.0, 6, 7
*Opera 11.5+
*HtmlUnit 2.9
*Android – 2.3+ for phones and tablets (devices & emulators)
*iOS 3+ for phones (devices & emulators) and 3.2+ for tablets (devices & emulators)

====Selenium 1 and Selenium IDE====
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Browser'''
| align="center" style="background:#f0f0f0;"|'''Selenium IDE'''
| align="center" style="background:#f0f0f0;"|'''Selenium 1 (RC)'''
| align="center" style="background:#f0f0f0;"|'''Operating Systems'''
|-
| Firefox 2, 3||Record and playback tests ||Start browser, run tests||Windows, Linux, Mac
|-
| IE 6, 7, 8||Unsupported ||Start browser, run tests||Windows
|-
| Safari 2, 3, 4||Unsupported ||Start browser, run tests||Windows, Mac
|-
| Opera 8, 9, 10||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
| Google Chrome||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
|}

===Advantage===
The chief advantages of Selenium are :
*Flexibility - Test automation can be customized by adding functionality to Selenium test scripts and Selenium framework.
*Open Source - The source code can be downloaded and modified as needed to suit new browsers.
*Deploys on multiple paltforms - Windows, Linux, and Macintosh.

More here

NOte ; can we add this http://aspyct.org/blog/2012/09/09/functional-web-testing-with-selenium-and-ruby/

==Auto Hot Key==
AutoHotkey automates tests by sending keystrokes and mouse clicks to the target application with the help of a macro recorder.
Virtually any key, button, or combination can become a hotkey.
Following are the notable features of hotkey:
* Expand abbreviations as you type them. For example, typing "gn" can automatically produce "good night".
* Create custom data-entry forms, user interfaces, and menu bars.
* Remap keys and buttons on your keyboard, joystick, and mouse.
* Convert any script into an EXE file that can be run on computers that don't have AutoHotkey installed.

Quick start tutorial : http://www.autohotkey.com/docs/Tutorial.htm

==Watir==
Watir, pronounced water, stands for Web Application Testing in Ruby. Watir is an open-source (BSD) family of Ruby libraries for automating web browsers. It is distributed as a Ruby GEM named 'Watir'. Watir drives browsers the same way people do. It clicks links, fills in forms, presses buttons. Watir also checks results, such as whether expected text appears on the page or not.

There are 2 version available :
* Watir-Classic : supports only Internet Explorer on Windows
* Watir-WebDriver : supports Chrome, Firefox, Internet Explorer, Opera and also running in headless mode (HTMLUnit).

==GNU Xnee==
GNU Xnee is a suite of programs that can record, replay and distribute user actions under the X11 environment. Xnee has the capability to :
* Automate tests like nightly regression
* Demonstrate programs by recording and replaying a user interaction with the system
* Distribute actions from system admin to end users.

The Record and replay ‘macro’ is the highlight of Xnee.

==DOJO==
Dojo is a JavaScript framework targeting the many needs of large-scale client-side web development.

* Dojo abstracts the differences among diverse browsers to provide APIs that will work on all of them (it can even run on the server under Node.js)
* It establishes a framework for defining modules of code and managing their inter-dependencies
* Supports internationalization, localization, and accessibility
* Provides a rich suite of commonly needed utility classes and user-interface widgets.

==CubicTest==
CubicTest is a graphical Eclipse plug-in for writing Selenium and Watir tests. It makes tests faster and easier to write, and provides abstractions to make tests more robust and reusable.

* CubicTest's test editor is centered around pages/states and transitions between these pages/states.
* The model is intuitive for both Ajax and traditional web applications and supports most user interaction types.
* CubicTest features an innovative test recorder and test runner based on Selenium RC which are fully integrated with the graphical test editor.

==Dogtail==
Dogtail is a GUI test tool and automation framework written in Python. It uses Accessibility (a11y) technologies to communicate with desktop applications. Dogtail scripts are written in Python and executed like any other Python program.
Follwoing are the notable features of Dogtail:
* Object-Oriented API: With the object oriented API, you are under control of the UI tree and its elements, allowing you to write sophisticated scripts utilizing benefits of OO right deep from dogtail.
* Procedural API: Ace programmer credentials are not necessary to write useful automated scripts with procedural API.
* Easily Extensible: Writing custom classes and helper libraries are easy.
* Results and debug reporting: Separate logs for test case comparisons and debug information are generated.

==Sikuli==
Sikuli automates GUI testing by using image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code.
* Sikuli uses an innovative approach of automating GUI tests by using screenshots and powerpoint slides.
* Sikuli Script is a visual scripting API using Jython to create automation scripts.
* Sikuli includes an integrated development environment (IDE) for writing visual Sikuli scripts with screenshots.

==See Also==
* Web testing tools [http://en.wikipedia.org/wiki/List_of_web_testing_tools]
* Selenium Framework [http://www.mediawiki.org/wiki/Selenium_Framework]
* Selenium [http://www.jroller.com/selenium/]

==References==
*http://docs.seleniumhq.org/docs/
*http://www.eecs.yorku.ca/course_archive/2004-05/W/4313/Slides/Module10-GUI.pdf
*http://www.cs.helsinki.fi/u/paakki/mikkolainen.pdf
*http://watir.com/
*http://www.gnu.org/software/xnee/
*https://fedorahosted.org/dogtail/
*http://www.cubictest.org/
*http://www.autohotkey.com/
*http://www.sikuli.org/

==Note to reviewers==
The topic is very vast. Hence the wiki is written based on the guidelines provided by the TA's and the Prof.
* List all GUI tools used in OSS that you can quickly identify.
* Try to describe the tools to the same level of detail, except that you may choose to go into more detail on tools that are used with Rails.
* Listing of commands is not a good idea. You are not writing a reference manual; you are writing a descriptive article that someone might read to learn about what's available before choosing a tool or tools. You should aim for readability.

We have referred the respective tool websites to provide the overview for each one of them. We have provided appropriate citations as well. Additionally the tool and the documentation itself are under GNU/ open source licence and hence will not fall under copyright violation. Please correct us if we are wrong.

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-07T23:45:22Z

Vshesha: /* GUI testing in Ruby and Rails */

==Introduction==
Graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its designed specifications.

GUI testing is difficult mainly due to following reasons :
* Large space of possibilities. Each sequence of GUI commands can result in various states. Evaluation of all these states is essential for validation of the GUI of the given software.
* Event-driven architecture. The test suite has to simulate the various user created actions.

Following are the challenges encountered while testing the graphical user interface of any software or system:
* Automation is difficult.
* The scope for testing is enormous
* Inability to determine the state of the program from GUI.
* Regression testing is difficult. Testcases may not be reusable

The current trend in user interfaces is geared towards graphical user interfaces (GUIs). This presents a problem for designing tests for software, since GUIs are very complex and hence GUI testing is very time consuming. Automation is a requirement for testing any larger graphical user interfaces, but automating GUI tests isn’t a straightforward task. Techniques which are familiar from the command line interface (CLI) age, don’t translate to the GUI world without problems.

==Test Automation==

Note : Rework

The advantages of test automation are as follows.
*Frequent regression testing
*Rapid feedback to developers - The earlier the problems are found, the cheaper it is to fix them. An automated unit test suite finds problems effectively as early as possible, long before the software reaches a customer, and even before it reaches the QA team.
*Virtually unlimited iterations of test case execution
*Support for Agile and extreme development methodologies
*Disciplined documentation of test cases
*Customized defect reporting
*Finding defects missed by manual testing

The challenge is in extending these advantages to GUI testing.

==GUI testing in Ruby and Rails==

Ruby prefers the term scripted testing over the more traditional automated testing. For testing a GUI application there can be several kind of tests in the background to verify the functionality and requirements of an application.

Various frameworks that support testing in Ruby are:
* Test:Unit - It is a unit testing framework for Ruby.
* Capybara - It is an integration testing tool for web applications.
* Rspec - Behaviour Driven Development (BDD) framework/ test tool
* Cucumber - It is a tool for running automated acceptance tests written in a behavior-driven development (BDD) style

Ruby on Rails testing frameworks are much more advanced than other web frameworks.

==GUI Testing Tools==

GUI testing tools serve the purpose of automating the testing process of software with graphical user interfaces. Following are few of the available open source GUI testing tools:

*AutoHotkey
*CubicTest
*Dogtail
*Dojo
*Selenium
*Watir
*GNU Xnee
*Sikuli

==Selenium==

===Introduction===
Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language (Selenium IDE). It also provides a test domain-specific language (Selenese) to write tests in a number of popular programming languages, including Java, C#, Groovy, Perl, PHP, Python and Ruby. The tests can then be run against most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.

===Selenium Tool Suite===
Selenium is composed of multiple software tools.

====Selenium IDE====
*Prototyping tool for building testscripts.
*Firefox plugin provides easy to use interface for developing automated tests.
*Supports 'record and play' feature to create reusable scripts for testing.

====Selenium1====
*Also known as Selenium RC or Remote Control
*Provides flexibility in porting tests across browsers and platforms.
*Currently in maintainence mode. No active development.

====Selenium 2====
*Also known as Selenium Webdriver
*Supports WebDriver API thus providing maximum flexibility in porting the tests.
*Runs Selenium 1’s Selenium RC interface for backwards compatibility.

====Selenium Grid====
*Selenium-Grid allows the Selenium RC solution to scale for large test suites and for test suites that must be run in multiple environments.
*Selenium Grid runs the tests in parallel, that is, different tests can be run at the same time on different remote machines.
*Selenium Grid greatly improves the time it takes to run the suite by making use of parallel processing.

===Supported Browsers and Platforms===

====Selenium 2====
*Google Chrome 12.0.712.0+
*Internet Explorer 6, 7, 8, 9 - 32 and 64-bit where applicable
*Firefox 3.0, 3.5, 3.6, 4.0, 5.0, 6, 7
*Opera 11.5+
*HtmlUnit 2.9
*Android – 2.3+ for phones and tablets (devices & emulators)
*iOS 3+ for phones (devices & emulators) and 3.2+ for tablets (devices & emulators)

====Selenium 1 and Selenium IDE====
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Browser'''
| align="center" style="background:#f0f0f0;"|'''Selenium IDE'''
| align="center" style="background:#f0f0f0;"|'''Selenium 1 (RC)'''
| align="center" style="background:#f0f0f0;"|'''Operating Systems'''
|-
| Firefox 2, 3||Record and playback tests ||Start browser, run tests||Windows, Linux, Mac
|-
| IE 6, 7, 8||Unsupported ||Start browser, run tests||Windows
|-
| Safari 2, 3, 4||Unsupported ||Start browser, run tests||Windows, Mac
|-
| Opera 8, 9, 10||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
| Google Chrome||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
|}

===Advantage===
The chief advantages of Selenium are :
*Flexibility - Test automation can be customized by adding functionality to Selenium test scripts and Selenium framework.
*Open Source - The source code can be downloaded and modified as needed to suit new browsers.
*Deploys on multiple paltforms - Windows, Linux, and Macintosh.

More here

NOte ; can we add this http://aspyct.org/blog/2012/09/09/functional-web-testing-with-selenium-and-ruby/

==Auto Hot Key==
AutoHotkey automates tests by sending keystrokes and mouse clicks to the target application with the help of a macro recorder.
Virtually any key, button, or combination can become a hotkey.
Following are the notable features of hotkey:
* Expand abbreviations as you type them. For example, typing "gn" can automatically produce "good night".
* Create custom data-entry forms, user interfaces, and menu bars.
* Remap keys and buttons on your keyboard, joystick, and mouse.
* Convert any script into an EXE file that can be run on computers that don't have AutoHotkey installed.

Quick start tutorial : http://www.autohotkey.com/docs/Tutorial.htm

==Watir==
Watir, pronounced water, stands for Web Application Testing in Ruby. Watir is an open-source (BSD) family of Ruby libraries for automating web browsers. It is distributed as a Ruby GEM named 'Watir'. Watir drives browsers the same way people do. It clicks links, fills in forms, presses buttons. Watir also checks results, such as whether expected text appears on the page or not.

There are 2 version available :
* Watir-Classic : supports only Internet Explorer on Windows
* Watir-WebDriver : supports Chrome, Firefox, Internet Explorer, Opera and also running in headless mode (HTMLUnit).

==GNU Xnee==
GNU Xnee is a suite of programs that can record, replay and distribute user actions under the X11 environment. Xnee has the capability to :
* Automate tests like nightly regression
* Demonstrate programs by recording and replaying a user interaction with the system
* Distribute actions from system admin to end users.

The Record and replay ‘macro’ is the highlight of Xnee.

==DOJO==
Dojo is a JavaScript framework targeting the many needs of large-scale client-side web development.

* Dojo abstracts the differences among diverse browsers to provide APIs that will work on all of them (it can even run on the server under Node.js)
* It establishes a framework for defining modules of code and managing their inter-dependencies
* Supports internationalization, localization, and accessibility
* Provides a rich suite of commonly needed utility classes and user-interface widgets.

==CubicTest==
CubicTest is a graphical Eclipse plug-in for writing Selenium and Watir tests. It makes tests faster and easier to write, and provides abstractions to make tests more robust and reusable.

* CubicTest's test editor is centered around pages/states and transitions between these pages/states.
* The model is intuitive for both Ajax and traditional web applications and supports most user interaction types.
* CubicTest features an innovative test recorder and test runner based on Selenium RC which are fully integrated with the graphical test editor.

==Dogtail==
Dogtail is a GUI test tool and automation framework written in Python. It uses Accessibility (a11y) technologies to communicate with desktop applications. Dogtail scripts are written in Python and executed like any other Python program.
Follwoing are the notable features of Dogtail:
* Object-Oriented API: With the object oriented API, you are under control of the UI tree and its elements, allowing you to write sophisticated scripts utilizing benefits of OO right deep from dogtail.
* Procedural API: Ace programmer credentials are not necessary to write useful automated scripts with procedural API.
* Easily Extensible: Writing custom classes and helper libraries are easy.
* Results and debug reporting: Separate logs for test case comparisons and debug information are generated.

==Sikuli==
Sikuli automates GUI testing by using image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code.
* Sikuli uses an innovative approach of automating GUI tests by using screenshots and powerpoint slides.
* Sikuli Script is a visual scripting API using Jython to create automation scripts.
* Sikuli includes an integrated development environment (IDE) for writing visual Sikuli scripts with screenshots.

==See Also==
[http://en.wikipedia.org/wiki/List_of_web_testing_tools]
[http://www.mediawiki.org/wiki/Selenium_Framework]
[http://www.jroller.com/selenium/]

==References==
*http://docs.seleniumhq.org/docs/
*http://www.eecs.yorku.ca/course_archive/2004-05/W/4313/Slides/Module10-GUI.pdf
*http://www.cs.helsinki.fi/u/paakki/mikkolainen.pdf
*http://watir.com/
*http://www.gnu.org/software/xnee/
*https://fedorahosted.org/dogtail/
*http://www.cubictest.org/
*http://www.autohotkey.com/
*http://www.sikuli.org/

==Note to reviewers==
The topic is very vast. Hence the wiki is written based on the guidelines provided by the TA's and the Prof.
* List all GUI tools used in OSS that you can quickly identify.
* Try to describe the tools to the same level of detail, except that you may choose to go into more detail on tools that are used with Rails.
* Listing of commands is not a good idea. You are not writing a reference manual; you are writing a descriptive article that someone might read to learn about what's available before choosing a tool or tools. You should aim for readability.

We have referred the respective tool websites to provide the overview for each one of them. We have provided appropriate citations as well. Additionally the tool and the documentation itself are under GNU/ open source licence and hence will not fall under copyright violation. Please correct us if we are wrong.

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-07T01:11:27Z

Vshesha: /* Selenium */

==Introduction==
Graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its designed specifications.

GUI testing is difficult mainly due to following reasons :
* Large space of possibilities. Each sequence of GUI commands can result in various states. Evaluation of all these states is essential for validation of the GUI of the given software.
* Event-driven architecture. The test suite has to simulate the various user created actions.

Following are the challenges encountered while testing the graphical user interface of any software or system:
* Automation is difficult.
* The scope for testing is enormous
* Inability to determine the state of the program from GUI.
* Regression testing is difficult. Testcases may not be reusable

The current trend in user interfaces is geared towards graphical user interfaces (GUIs). This presents a problem for designing tests for software, since GUIs are very complex and hence GUI testing is very time consuming. Automation is a requirement for testing any larger graphical user interfaces, but automating GUI tests isn’t a straightforward task. Techniques which are familiar from the command line interface (CLI) age, don’t translate to the GUI world without problems.

==Test Automation==

Note : Rework

The advantages of test automation are as follows.
*Frequent regression testing
*Rapid feedback to developers
*Virtually unlimited iterations of test case execution
*Support for Agile and extreme development methodologies
*Disciplined documentation of test cases
*Customized defect reporting
*Finding defects missed by manual testing

The challenge is in extending these advantages to GUI testing.

==GUI testing in Ruby and Rails==

==GUI Testing Tools==

GUI testing tools serve the purpose of automating the testing process of software with graphical user interfaces. Following are few of the available open source GUI testing tools:

*AutoHotkey
*CubicTest
*Dogtail
*Dojo
*Selenium
*Watir
*GNU Xnee
*Sikuli

==Selenium==

===Introduction===
Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language (Selenium IDE). It also provides a test domain-specific language (Selenese) to write tests in a number of popular programming languages, including Java, C#, Groovy, Perl, PHP, Python and Ruby. The tests can then be run against most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.

===Selenium Tool Suite===
Selenium is composed of multiple software tools.

====Selenium IDE====
*Prototyping tool for building testscripts.
*Firefox plugin provides easy to use interface for developing automated tests.
*Supports 'record and play' feature to create reusable scripts for testing.

====Selenium1====
*Also known as Selenium RC or Remote Control
*Provides flexibility in porting tests across browsers and platforms.
*Currently in maintainence mode. No active development.

====Selenium 2====
*Also known as Selenium Webdriver
*Supports WebDriver API thus providing maximum flexibility in porting the tests.
*Runs Selenium 1’s Selenium RC interface for backwards compatibility.

====Selenium Grid====
*Selenium-Grid allows the Selenium RC solution to scale for large test suites and for test suites that must be run in multiple environments.
*Selenium Grid runs the tests in parallel, that is, different tests can be run at the same time on different remote machines.
*Selenium Grid greatly improves the time it takes to run the suite by making use of parallel processing.

===Supported Browsers and Platforms===
====Selenium 2====
*Google Chrome 12.0.712.0+
*Internet Explorer 6, 7, 8, 9 - 32 and 64-bit where applicable
*Firefox 3.0, 3.5, 3.6, 4.0, 5.0, 6, 7
*Opera 11.5+
*HtmlUnit 2.9
*Android – 2.3+ for phones and tablets (devices & emulators)
*iOS 3+ for phones (devices & emulators) and 3.2+ for tablets (devices & emulators)

====Selenium 1 and Selenium IDE====
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Browser'''
| align="center" style="background:#f0f0f0;"|'''Selenium IDE'''
| align="center" style="background:#f0f0f0;"|'''Selenium 1 (RC)'''
| align="center" style="background:#f0f0f0;"|'''Operating Systems'''
|-
| Firefox 2, 3||Record and playback tests ||Start browser, run tests||Windows, Linux, Mac
|-
| IE 6, 7, 8||Unsupported ||Start browser, run tests||Windows
|-
| Safari 2, 3, 4||Unsupported ||Start browser, run tests||Windows, Mac
|-
| Opera 8, 9, 10||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
| Google Chrome||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
|}

===Advantage===
The chief advantages of Selenium are :
*Flexibility - Test automation can be customized by adding functionality to Selenium test scripts and Selenium framework.
*Open Source - The source code can be downloaded and modified as needed to suit new browsers.

More here

NOte ; can we add this http://aspyct.org/blog/2012/09/09/functional-web-testing-with-selenium-and-ruby/

==Auto Hot Key==
AutoHotkey automates tests by sending keystrokes and mouse clicks to the target application with the help of a macro recorder.
Virtually any key, button, or combination can become a hotkey.
Following are the notable features of hotkey:
* Expand abbreviations as you type them. For example, typing "gn" can automatically produce "good night".
* Create custom data-entry forms, user interfaces, and menu bars.
* Remap keys and buttons on your keyboard, joystick, and mouse.
* Convert any script into an EXE file that can be run on computers that don't have AutoHotkey installed.

Quick start tutorial : http://www.autohotkey.com/docs/Tutorial.htm

==Watir==
Watir, pronounced water, stands for Web Application Testing in Ruby. Watir is an open-source (BSD) family of Ruby libraries for automating web browsers. It is distributed as a Ruby GEM named 'Watir'. Watir drives browsers the same way people do. It clicks links, fills in forms, presses buttons. Watir also checks results, such as whether expected text appears on the page or not.

There are 2 version available :
* Watir-Classic : supports only Internet Explorer on Windows
* Watir-WebDriver : supports Chrome, Firefox, Internet Explorer, Opera and also running in headless mode (HTMLUnit).

==GNU Xnee==
GNU Xnee is a suite of programs that can record, replay and distribute user actions under the X11 environment. Xnee has the capability to :
* Automate tests like nightly regression
* Demonstrate programs by recording and replaying a user interaction with the system
* Distribute actions from system admin to end users.

The Record and replay ‘macro’ is the highlight of Xnee.

==DOJO==
Dojo is a JavaScript framework targeting the many needs of large-scale client-side web development.

* Dojo abstracts the differences among diverse browsers to provide APIs that will work on all of them (it can even run on the server under Node.js)
* It establishes a framework for defining modules of code and managing their inter-dependencies
* Supports internationalization, localization, and accessibility
* Provides a rich suite of commonly needed utility classes and user-interface widgets.

==CubicTest==
CubicTest is a graphical Eclipse plug-in for writing Selenium and Watir tests. It makes tests faster and easier to write, and provides abstractions to make tests more robust and reusable.

* CubicTest's test editor is centered around pages/states and transitions between these pages/states.
* The model is intuitive for both Ajax and traditional web applications and supports most user interaction types.
* CubicTest features an innovative test recorder and test runner based on Selenium RC which are fully integrated with the graphical test editor.

==Dogtail==
Dogtail is a GUI test tool and automation framework written in Python. It uses Accessibility (a11y) technologies to communicate with desktop applications. Dogtail scripts are written in Python and executed like any other Python program.
Follwoing are the notable features of Dogtail:
* Object-Oriented API: With the object oriented API, you are under control of the UI tree and its elements, allowing you to write sophisticated scripts utilizing benefits of OO right deep from dogtail.
* Procedural API: Ace programmer credentials are not necessary to write useful automated scripts with procedural API.
* Easily Extensible: Writing custom classes and helper libraries are easy.
* Results and debug reporting: Separate logs for test case comparisons and debug information are generated.

==Sikuli==
Sikuli automates GUI testing by using image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code.
* Sikuli uses an innovative approach of automating GUI tests by using screenshots and powerpoint slides.
* Sikuli Script is a visual scripting API using Jython to create automation scripts.
* Sikuli includes an integrated development environment (IDE) for writing visual Sikuli scripts with screenshots.

==See Also==
==References==
*http://docs.seleniumhq.org/docs/
*http://www.eecs.yorku.ca/course_archive/2004-05/W/4313/Slides/Module10-GUI.pdf
*http://www.cs.helsinki.fi/u/paakki/mikkolainen.pdf
*http://watir.com/
*http://www.gnu.org/software/xnee/
*https://fedorahosted.org/dogtail/
*http://www.cubictest.org/
*http://www.autohotkey.com/
*http://www.sikuli.org/

==Note to reviewers==
The topic is very vast. Hence the wiki is written based on the guidelines provided by the TA's and the Prof.
* List all GUI tools used in OSS that you can quickly identify.
* Try to describe the tools to the same level of detail, except that you may choose to go into more detail on tools that are used with Rails.
* Listing of commands is not a good idea. You are not writing a reference manual; you are writing a descriptive article that someone might read to learn about what's available before choosing a tool or tools. You should aim for readability.

We have referred the respective tool websites to provide the overview for each one of them. We have provided appropriate citations as well. Additionally the tool and the documentation itself are under GNU/ open source licence and hence will not fall under copyright violation. Please correct us if we are wrong.

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-07T01:09:21Z

Vshesha: /* GUI testing in Ruby */

==Introduction==
Graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its designed specifications.

GUI testing is difficult mainly due to following reasons :
* Large space of possibilities. Each sequence of GUI commands can result in various states. Evaluation of all these states is essential for validation of the GUI of the given software.
* Event-driven architecture. The test suite has to simulate the various user created actions.

Following are the challenges encountered while testing the graphical user interface of any software or system:
* Automation is difficult.
* The scope for testing is enormous
* Inability to determine the state of the program from GUI.
* Regression testing is difficult. Testcases may not be reusable

The current trend in user interfaces is geared towards graphical user interfaces (GUIs). This presents a problem for designing tests for software, since GUIs are very complex and hence GUI testing is very time consuming. Automation is a requirement for testing any larger graphical user interfaces, but automating GUI tests isn’t a straightforward task. Techniques which are familiar from the command line interface (CLI) age, don’t translate to the GUI world without problems.

==Test Automation==

Note : Rework

The advantages of test automation are as follows.
*Frequent regression testing
*Rapid feedback to developers
*Virtually unlimited iterations of test case execution
*Support for Agile and extreme development methodologies
*Disciplined documentation of test cases
*Customized defect reporting
*Finding defects missed by manual testing

The challenge is in extending these advantages to GUI testing.

==GUI testing in Ruby and Rails==

==GUI Testing Tools==

GUI testing tools serve the purpose of automating the testing process of software with graphical user interfaces. Following are few of the available open source GUI testing tools:

*AutoHotkey
*CubicTest
*Dogtail
*Dojo
*Selenium
*Watir
*GNU Xnee
*Sikuli

==Selenium==

===Introduction===
Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language (Selenium IDE). It also provides a test domain-specific language (Selenese) to write tests in a number of popular programming languages, including Java, C#, Groovy, Perl, PHP, Python and Ruby. The tests can then be run against most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.

===Selenium Tool Suite===
Selenium is composed of multiple software tools.

====Selenium IDE====
*Prototyping tool for building testscripts.
*Firefox plugin provides easy to use interface for developing automated tests.
*Supports 'record and play' feature to create reusable scripts for testing.

====Selenium1====
*Also known as Selenium RC or Remote Control
*Provides flexibility in porting tests across browsers and platforms.
*Currently in maintainence mode. No active development.

====Selenium 2====
*Also known as Selenium Webdriver
*Supports WebDriver API thus providing maximum flexibility in porting the tests.
*Runs Selenium 1’s Selenium RC interface for backwards compatibility.

====Selenium Grid====
*Selenium-Grid allows the Selenium RC solution to scale for large test suites and for test suites that must be run in multiple environments.
*Selenium Grid runs the tests in parallel, that is, different tests can be run at the same time on different remote machines.
*Selenium Grid greatly improves the time it takes to run the suite by making use of parallel processing.

===Supported Browsers and Platforms===
====Selenium 2====
*Google Chrome 12.0.712.0+
*Internet Explorer 6, 7, 8, 9 - 32 and 64-bit where applicable
*Firefox 3.0, 3.5, 3.6, 4.0, 5.0, 6, 7
*Opera 11.5+
*HtmlUnit 2.9
*Android – 2.3+ for phones and tablets (devices & emulators)
*iOS 3+ for phones (devices & emulators) and 3.2+ for tablets (devices & emulators)

====Selenium 1 and Selenium IDE====
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Browser'''
| align="center" style="background:#f0f0f0;"|'''Selenium IDE'''
| align="center" style="background:#f0f0f0;"|'''Selenium 1 (RC)'''
| align="center" style="background:#f0f0f0;"|'''Operating Systems'''
|-
| Firefox 2, 3||Record and playback tests ||Start browser, run tests||Windows, Linux, Mac
|-
| IE 6, 7, 8||Unsupported ||Start browser, run tests||Windows
|-
| Safari 2, 3, 4||Unsupported ||Start browser, run tests||Windows, Mac
|-
| Opera 8, 9, 10||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
| Google Chrome||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
|}

===Advantage===
The chief advantages of Selenium are :
*Flexibility - Test automation can be customized by adding functionality to Selenium test scripts and Selenium framework.
*Open Source - The source code can be downloaded and modified as needed to suit new browsers.

==Auto Hot Key==
AutoHotkey automates tests by sending keystrokes and mouse clicks to the target application with the help of a macro recorder.
Virtually any key, button, or combination can become a hotkey.
Following are the notable features of hotkey:
* Expand abbreviations as you type them. For example, typing "gn" can automatically produce "good night".
* Create custom data-entry forms, user interfaces, and menu bars.
* Remap keys and buttons on your keyboard, joystick, and mouse.
* Convert any script into an EXE file that can be run on computers that don't have AutoHotkey installed.

Quick start tutorial : http://www.autohotkey.com/docs/Tutorial.htm

==Watir==
Watir, pronounced water, stands for Web Application Testing in Ruby. Watir is an open-source (BSD) family of Ruby libraries for automating web browsers. It is distributed as a Ruby GEM named 'Watir'. Watir drives browsers the same way people do. It clicks links, fills in forms, presses buttons. Watir also checks results, such as whether expected text appears on the page or not.

There are 2 version available :
* Watir-Classic : supports only Internet Explorer on Windows
* Watir-WebDriver : supports Chrome, Firefox, Internet Explorer, Opera and also running in headless mode (HTMLUnit).

==GNU Xnee==
GNU Xnee is a suite of programs that can record, replay and distribute user actions under the X11 environment. Xnee has the capability to :
* Automate tests like nightly regression
* Demonstrate programs by recording and replaying a user interaction with the system
* Distribute actions from system admin to end users.

The Record and replay ‘macro’ is the highlight of Xnee.

==DOJO==
Dojo is a JavaScript framework targeting the many needs of large-scale client-side web development.

* Dojo abstracts the differences among diverse browsers to provide APIs that will work on all of them (it can even run on the server under Node.js)
* It establishes a framework for defining modules of code and managing their inter-dependencies
* Supports internationalization, localization, and accessibility
* Provides a rich suite of commonly needed utility classes and user-interface widgets.

==CubicTest==
CubicTest is a graphical Eclipse plug-in for writing Selenium and Watir tests. It makes tests faster and easier to write, and provides abstractions to make tests more robust and reusable.

* CubicTest's test editor is centered around pages/states and transitions between these pages/states.
* The model is intuitive for both Ajax and traditional web applications and supports most user interaction types.
* CubicTest features an innovative test recorder and test runner based on Selenium RC which are fully integrated with the graphical test editor.

==Dogtail==
Dogtail is a GUI test tool and automation framework written in Python. It uses Accessibility (a11y) technologies to communicate with desktop applications. Dogtail scripts are written in Python and executed like any other Python program.
Follwoing are the notable features of Dogtail:
* Object-Oriented API: With the object oriented API, you are under control of the UI tree and its elements, allowing you to write sophisticated scripts utilizing benefits of OO right deep from dogtail.
* Procedural API: Ace programmer credentials are not necessary to write useful automated scripts with procedural API.
* Easily Extensible: Writing custom classes and helper libraries are easy.
* Results and debug reporting: Separate logs for test case comparisons and debug information are generated.

==Sikuli==
Sikuli automates GUI testing by using image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code.
* Sikuli uses an innovative approach of automating GUI tests by using screenshots and powerpoint slides.
* Sikuli Script is a visual scripting API using Jython to create automation scripts.
* Sikuli includes an integrated development environment (IDE) for writing visual Sikuli scripts with screenshots.

==See Also==
==References==
*http://docs.seleniumhq.org/docs/
*http://www.eecs.yorku.ca/course_archive/2004-05/W/4313/Slides/Module10-GUI.pdf
*http://www.cs.helsinki.fi/u/paakki/mikkolainen.pdf
*http://watir.com/
*http://www.gnu.org/software/xnee/
*https://fedorahosted.org/dogtail/
*http://www.cubictest.org/
*http://www.autohotkey.com/
*http://www.sikuli.org/

==Note to reviewers==
The topic is very vast. Hence the wiki is written based on the guidelines provided by the TA's and the Prof.
* List all GUI tools used in OSS that you can quickly identify.
* Try to describe the tools to the same level of detail, except that you may choose to go into more detail on tools that are used with Rails.
* Listing of commands is not a good idea. You are not writing a reference manual; you are writing a descriptive article that someone might read to learn about what's available before choosing a tool or tools. You should aim for readability.

We have referred the respective tool websites to provide the overview for each one of them. We have provided appropriate citations as well. Additionally the tool and the documentation itself are under GNU/ open source licence and hence will not fall under copyright violation. Please correct us if we are wrong.

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-07T01:08:56Z

Vshesha: /* Test Automation */

==Introduction==
Graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its designed specifications.

GUI testing is difficult mainly due to following reasons :
* Large space of possibilities. Each sequence of GUI commands can result in various states. Evaluation of all these states is essential for validation of the GUI of the given software.
* Event-driven architecture. The test suite has to simulate the various user created actions.

Following are the challenges encountered while testing the graphical user interface of any software or system:
* Automation is difficult.
* The scope for testing is enormous
* Inability to determine the state of the program from GUI.
* Regression testing is difficult. Testcases may not be reusable

The current trend in user interfaces is geared towards graphical user interfaces (GUIs). This presents a problem for designing tests for software, since GUIs are very complex and hence GUI testing is very time consuming. Automation is a requirement for testing any larger graphical user interfaces, but automating GUI tests isn’t a straightforward task. Techniques which are familiar from the command line interface (CLI) age, don’t translate to the GUI world without problems.

==Test Automation==

Note : Rework

The advantages of test automation are as follows.
*Frequent regression testing
*Rapid feedback to developers
*Virtually unlimited iterations of test case execution
*Support for Agile and extreme development methodologies
*Disciplined documentation of test cases
*Customized defect reporting
*Finding defects missed by manual testing

The challenge is in extending these advantages to GUI testing.

==GUI testing in Ruby==
==GUI Testing Tools==

GUI testing tools serve the purpose of automating the testing process of software with graphical user interfaces. Following are few of the available open source GUI testing tools:

*AutoHotkey
*CubicTest
*Dogtail
*Dojo
*Selenium
*Watir
*GNU Xnee
*Sikuli

==Selenium==

===Introduction===
Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language (Selenium IDE). It also provides a test domain-specific language (Selenese) to write tests in a number of popular programming languages, including Java, C#, Groovy, Perl, PHP, Python and Ruby. The tests can then be run against most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.

===Selenium Tool Suite===
Selenium is composed of multiple software tools.

====Selenium IDE====
*Prototyping tool for building testscripts.
*Firefox plugin provides easy to use interface for developing automated tests.
*Supports 'record and play' feature to create reusable scripts for testing.

====Selenium1====
*Also known as Selenium RC or Remote Control
*Provides flexibility in porting tests across browsers and platforms.
*Currently in maintainence mode. No active development.

====Selenium 2====
*Also known as Selenium Webdriver
*Supports WebDriver API thus providing maximum flexibility in porting the tests.
*Runs Selenium 1’s Selenium RC interface for backwards compatibility.

====Selenium Grid====
*Selenium-Grid allows the Selenium RC solution to scale for large test suites and for test suites that must be run in multiple environments.
*Selenium Grid runs the tests in parallel, that is, different tests can be run at the same time on different remote machines.
*Selenium Grid greatly improves the time it takes to run the suite by making use of parallel processing.

===Supported Browsers and Platforms===
====Selenium 2====
*Google Chrome 12.0.712.0+
*Internet Explorer 6, 7, 8, 9 - 32 and 64-bit where applicable
*Firefox 3.0, 3.5, 3.6, 4.0, 5.0, 6, 7
*Opera 11.5+
*HtmlUnit 2.9
*Android – 2.3+ for phones and tablets (devices & emulators)
*iOS 3+ for phones (devices & emulators) and 3.2+ for tablets (devices & emulators)

====Selenium 1 and Selenium IDE====
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Browser'''
| align="center" style="background:#f0f0f0;"|'''Selenium IDE'''
| align="center" style="background:#f0f0f0;"|'''Selenium 1 (RC)'''
| align="center" style="background:#f0f0f0;"|'''Operating Systems'''
|-
| Firefox 2, 3||Record and playback tests ||Start browser, run tests||Windows, Linux, Mac
|-
| IE 6, 7, 8||Unsupported ||Start browser, run tests||Windows
|-
| Safari 2, 3, 4||Unsupported ||Start browser, run tests||Windows, Mac
|-
| Opera 8, 9, 10||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
| Google Chrome||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
|}

===Advantage===
The chief advantages of Selenium are :
*Flexibility - Test automation can be customized by adding functionality to Selenium test scripts and Selenium framework.
*Open Source - The source code can be downloaded and modified as needed to suit new browsers.

==Auto Hot Key==
AutoHotkey automates tests by sending keystrokes and mouse clicks to the target application with the help of a macro recorder.
Virtually any key, button, or combination can become a hotkey.
Following are the notable features of hotkey:
* Expand abbreviations as you type them. For example, typing "gn" can automatically produce "good night".
* Create custom data-entry forms, user interfaces, and menu bars.
* Remap keys and buttons on your keyboard, joystick, and mouse.
* Convert any script into an EXE file that can be run on computers that don't have AutoHotkey installed.

Quick start tutorial : http://www.autohotkey.com/docs/Tutorial.htm

==Watir==
Watir, pronounced water, stands for Web Application Testing in Ruby. Watir is an open-source (BSD) family of Ruby libraries for automating web browsers. It is distributed as a Ruby GEM named 'Watir'. Watir drives browsers the same way people do. It clicks links, fills in forms, presses buttons. Watir also checks results, such as whether expected text appears on the page or not.

There are 2 version available :
* Watir-Classic : supports only Internet Explorer on Windows
* Watir-WebDriver : supports Chrome, Firefox, Internet Explorer, Opera and also running in headless mode (HTMLUnit).

==GNU Xnee==
GNU Xnee is a suite of programs that can record, replay and distribute user actions under the X11 environment. Xnee has the capability to :
* Automate tests like nightly regression
* Demonstrate programs by recording and replaying a user interaction with the system
* Distribute actions from system admin to end users.

The Record and replay ‘macro’ is the highlight of Xnee.

==DOJO==
Dojo is a JavaScript framework targeting the many needs of large-scale client-side web development.

* Dojo abstracts the differences among diverse browsers to provide APIs that will work on all of them (it can even run on the server under Node.js)
* It establishes a framework for defining modules of code and managing their inter-dependencies
* Supports internationalization, localization, and accessibility
* Provides a rich suite of commonly needed utility classes and user-interface widgets.

==CubicTest==
CubicTest is a graphical Eclipse plug-in for writing Selenium and Watir tests. It makes tests faster and easier to write, and provides abstractions to make tests more robust and reusable.

* CubicTest's test editor is centered around pages/states and transitions between these pages/states.
* The model is intuitive for both Ajax and traditional web applications and supports most user interaction types.
* CubicTest features an innovative test recorder and test runner based on Selenium RC which are fully integrated with the graphical test editor.

==Dogtail==
Dogtail is a GUI test tool and automation framework written in Python. It uses Accessibility (a11y) technologies to communicate with desktop applications. Dogtail scripts are written in Python and executed like any other Python program.
Follwoing are the notable features of Dogtail:
* Object-Oriented API: With the object oriented API, you are under control of the UI tree and its elements, allowing you to write sophisticated scripts utilizing benefits of OO right deep from dogtail.
* Procedural API: Ace programmer credentials are not necessary to write useful automated scripts with procedural API.
* Easily Extensible: Writing custom classes and helper libraries are easy.
* Results and debug reporting: Separate logs for test case comparisons and debug information are generated.

==Sikuli==
Sikuli automates GUI testing by using image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code.
* Sikuli uses an innovative approach of automating GUI tests by using screenshots and powerpoint slides.
* Sikuli Script is a visual scripting API using Jython to create automation scripts.
* Sikuli includes an integrated development environment (IDE) for writing visual Sikuli scripts with screenshots.

==See Also==
==References==
*http://docs.seleniumhq.org/docs/
*http://www.eecs.yorku.ca/course_archive/2004-05/W/4313/Slides/Module10-GUI.pdf
*http://www.cs.helsinki.fi/u/paakki/mikkolainen.pdf
*http://watir.com/
*http://www.gnu.org/software/xnee/
*https://fedorahosted.org/dogtail/
*http://www.cubictest.org/
*http://www.autohotkey.com/
*http://www.sikuli.org/

==Note to reviewers==
The topic is very vast. Hence the wiki is written based on the guidelines provided by the TA's and the Prof.
* List all GUI tools used in OSS that you can quickly identify.
* Try to describe the tools to the same level of detail, except that you may choose to go into more detail on tools that are used with Rails.
* Listing of commands is not a good idea. You are not writing a reference manual; you are writing a descriptive article that someone might read to learn about what's available before choosing a tool or tools. You should aim for readability.

We have referred the respective tool websites to provide the overview for each one of them. We have provided appropriate citations as well. Additionally the tool and the documentation itself are under GNU/ open source licence and hence will not fall under copyright violation. Please correct us if we are wrong.

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-07T00:19:56Z

Vshesha: /* Supported Browsers and Platforms */

==Introduction==
Graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its designed specifications.

GUI testing is difficult mainly due to following reasons :
* Large space of possibilities. Each sequence of GUI commands can result in various states. Evaluation of all these states is essential for validation of the GUI of the given software.
* Event-driven architecture. The test suite has to simulate the various user created actions.

Following are the challenges encountered while testing the graphical user interface of any software or system:
* Automation is difficult.
* The scope for testing is enormous
* Inability to determine the state of the program from GUI.
* Regression testing is difficult. Testcases may not be reusable

The current trend in user interfaces is geared towards graphical user interfaces (GUIs). This presents a problem for designing tests for software, since GUIs are very complex and hence GUI testing is very time consuming. Automation is a requirement for testing any larger graphical user interfaces, but automating GUI tests isn’t a straightforward task. Techniques which are familiar from the command line interface (CLI) age, don’t translate to the GUI world without problems.

==Test Automation==
The advantages of test automation are as follows.
*Frequent regression testing
*Rapid feedback to developers
*Virtually unlimited iterations of test case execution
*Support for Agile and extreme development methodologies
*Disciplined documentation of test cases
*Customized defect reporting
*Finding defects missed by manual testing

The challenge is in extending these advantages to GUI testing.

==GUI testing in Ruby==
==GUI Testing Tools==

GUI testing tools serve the purpose of automating the testing process of software with graphical user interfaces. Following are few of the available open source GUI testing tools:

*AutoHotkey
*CubicTest
*Dogtail
*Dojo
*Selenium
*Watir
*GNU Xnee
*Sikuli

==Selenium==

===Introduction===
Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language (Selenium IDE). It also provides a test domain-specific language (Selenese) to write tests in a number of popular programming languages, including Java, C#, Groovy, Perl, PHP, Python and Ruby. The tests can then be run against most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.

===Selenium Tool Suite===
Selenium is composed of multiple software tools.

====Selenium IDE====
*Prototyping tool for building testscripts.
*Firefox plugin provides easy to use interface for developing automated tests.
*Supports 'record and play' feature to create reusable scripts for testing.

====Selenium1====
*Also known as Selenium RC or Remote Control
*Provides flexibility in porting tests across browsers and platforms.
*Currently in maintainence mode. No active development.

====Selenium 2====
*Also known as Selenium Webdriver
*Supports WebDriver API thus providing maximum flexibility in porting the tests.
*Runs Selenium 1’s Selenium RC interface for backwards compatibility.

====Selenium Grid====
*Selenium-Grid allows the Selenium RC solution to scale for large test suites and for test suites that must be run in multiple environments.
*Selenium Grid runs the tests in parallel, that is, different tests can be run at the same time on different remote machines.
*Selenium Grid greatly improves the time it takes to run the suite by making use of parallel processing.

===Supported Browsers and Platforms===
====Selenium 2====
*Google Chrome 12.0.712.0+
*Internet Explorer 6, 7, 8, 9 - 32 and 64-bit where applicable
*Firefox 3.0, 3.5, 3.6, 4.0, 5.0, 6, 7
*Opera 11.5+
*HtmlUnit 2.9
*Android – 2.3+ for phones and tablets (devices & emulators)
*iOS 3+ for phones (devices & emulators) and 3.2+ for tablets (devices & emulators)

====Selenium 1 and Selenium IDE====
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Browser'''
| align="center" style="background:#f0f0f0;"|'''Selenium IDE'''
| align="center" style="background:#f0f0f0;"|'''Selenium 1 (RC)'''
| align="center" style="background:#f0f0f0;"|'''Operating Systems'''
|-
| Firefox 2, 3||Record and playback tests ||Start browser, run tests||Windows, Linux, Mac
|-
| IE 6, 7, 8||Unsupported ||Start browser, run tests||Windows
|-
| Safari 2, 3, 4||Unsupported ||Start browser, run tests||Windows, Mac
|-
| Opera 8, 9, 10||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
| Google Chrome||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
|}

===Advantage===
The chief advantages of Selenium are :
*Flexibility - Test automation can be customized by adding functionality to Selenium test scripts and Selenium framework.
*Open Source - The source code can be downloaded and modified as needed to suit new browsers.

==Auto Hot Key==
AutoHotkey automates tests by sending keystrokes and mouse clicks to the target application with the help of a macro recorder.
Virtually any key, button, or combination can become a hotkey.
Following are the notable features of hotkey:
* Expand abbreviations as you type them. For example, typing "gn" can automatically produce "good night".
* Create custom data-entry forms, user interfaces, and menu bars.
* Remap keys and buttons on your keyboard, joystick, and mouse.
* Convert any script into an EXE file that can be run on computers that don't have AutoHotkey installed.

Quick start tutorial : http://www.autohotkey.com/docs/Tutorial.htm

==Watir==
Watir, pronounced water, stands for Web Application Testing in Ruby. Watir is an open-source (BSD) family of Ruby libraries for automating web browsers. It is distributed as a Ruby GEM named 'Watir'. Watir drives browsers the same way people do. It clicks links, fills in forms, presses buttons. Watir also checks results, such as whether expected text appears on the page or not.

There are 2 version available :
* Watir-Classic : supports only Internet Explorer on Windows
* Watir-WebDriver : supports Chrome, Firefox, Internet Explorer, Opera and also running in headless mode (HTMLUnit).

==GNU Xnee==
GNU Xnee is a suite of programs that can record, replay and distribute user actions under the X11 environment. Xnee has the capability to :
* Automate tests like nightly regression
* Demonstrate programs by recording and replaying a user interaction with the system
* Distribute actions from system admin to end users.

The Record and replay ‘macro’ is the highlight of Xnee.

==DOJO==
Dojo is a JavaScript framework targeting the many needs of large-scale client-side web development.

* Dojo abstracts the differences among diverse browsers to provide APIs that will work on all of them (it can even run on the server under Node.js)
* It establishes a framework for defining modules of code and managing their inter-dependencies
* Supports internationalization, localization, and accessibility
* Provides a rich suite of commonly needed utility classes and user-interface widgets.

==CubicTest==
CubicTest is a graphical Eclipse plug-in for writing Selenium and Watir tests. It makes tests faster and easier to write, and provides abstractions to make tests more robust and reusable.

* CubicTest's test editor is centered around pages/states and transitions between these pages/states.
* The model is intuitive for both Ajax and traditional web applications and supports most user interaction types.
* CubicTest features an innovative test recorder and test runner based on Selenium RC which are fully integrated with the graphical test editor.

==Dogtail==
Dogtail is a GUI test tool and automation framework written in Python. It uses Accessibility (a11y) technologies to communicate with desktop applications. Dogtail scripts are written in Python and executed like any other Python program.
Follwoing are the notable features of Dogtail:
* Object-Oriented API: With the object oriented API, you are under control of the UI tree and its elements, allowing you to write sophisticated scripts utilizing benefits of OO right deep from dogtail.
* Procedural API: Ace programmer credentials are not necessary to write useful automated scripts with procedural API.
* Easily Extensible: Writing custom classes and helper libraries are easy.
* Results and debug reporting: Separate logs for test case comparisons and debug information are generated.

==Sikuli==
Sikuli automates GUI testing by using image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code.
* Sikuli uses an innovative approach of automating GUI tests by using screenshots and powerpoint slides.
* Sikuli Script is a visual scripting API using Jython to create automation scripts.
* Sikuli includes an integrated development environment (IDE) for writing visual Sikuli scripts with screenshots.

==See Also==
==References==
*http://docs.seleniumhq.org/docs/
*http://www.eecs.yorku.ca/course_archive/2004-05/W/4313/Slides/Module10-GUI.pdf
*http://www.cs.helsinki.fi/u/paakki/mikkolainen.pdf
*http://watir.com/
*http://www.gnu.org/software/xnee/
*https://fedorahosted.org/dogtail/
*http://www.cubictest.org/
*http://www.autohotkey.com/
*http://www.sikuli.org/

==Note to reviewers==
The topic is very vast. Hence the wiki is written based on the guidelines provided by the TA's and the Prof.
* List all GUI tools used in OSS that you can quickly identify.
* Try to describe the tools to the same level of detail, except that you may choose to go into more detail on tools that are used with Rails.
* Listing of commands is not a good idea. You are not writing a reference manual; you are writing a descriptive article that someone might read to learn about what's available before choosing a tool or tools. You should aim for readability.

We have referred the respective tool websites to provide the overview for each one of them. We have provided appropriate citations as well. Additionally the tool and the documentation itself are under GNU/ open source licence and hence will not fall under copyright violation. Please correct us if we are wrong.

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-07T00:15:49Z

Vshesha: /* Selenium 1 and Selenium IDE */

==Introduction==
Graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its designed specifications.

GUI testing is difficult mainly due to following reasons :
* Large space of possibilities. Each sequence of GUI commands can result in various states. Evaluation of all these states is essential for validation of the GUI of the given software.
* Event-driven architecture. The test suite has to simulate the various user created actions.

Following are the challenges encountered while testing the graphical user interface of any software or system:
* Automation is difficult.
* The scope for testing is enormous
* Inability to determine the state of the program from GUI.
* Regression testing is difficult. Testcases may not be reusable

The current trend in user interfaces is geared towards graphical user interfaces (GUIs). This presents a problem for designing tests for software, since GUIs are very complex and hence GUI testing is very time consuming. Automation is a requirement for testing any larger graphical user interfaces, but automating GUI tests isn’t a straightforward task. Techniques which are familiar from the command line interface (CLI) age, don’t translate to the GUI world without problems.

==Test Automation==
The advantages of test automation are as follows.
*Frequent regression testing
*Rapid feedback to developers
*Virtually unlimited iterations of test case execution
*Support for Agile and extreme development methodologies
*Disciplined documentation of test cases
*Customized defect reporting
*Finding defects missed by manual testing

The challenge is in extending these advantages to GUI testing.

==GUI testing in Ruby==
==GUI Testing Tools==

GUI testing tools serve the purpose of automating the testing process of software with graphical user interfaces. Following are few of the available open source GUI testing tools:

*AutoHotkey
*CubicTest
*Dogtail
*Dojo
*Selenium
*Watir
*GNU Xnee
*Sikuli

==Selenium==

===Introduction===
Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language (Selenium IDE). It also provides a test domain-specific language (Selenese) to write tests in a number of popular programming languages, including Java, C#, Groovy, Perl, PHP, Python and Ruby. The tests can then be run against most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.

===Selenium Tool Suite===
Selenium is composed of multiple software tools.

====Selenium IDE====
*Prototyping tool for building testscripts.
*Firefox plugin provides easy to use interface for developing automated tests.
*Supports 'record and play' feature to create reusable scripts for testing.

====Selenium1====
*Also known as Selenium RC or Remote Control
*Provides flexibility in porting tests across browsers and platforms.
*Currently in maintainence mode. No active development.

====Selenium 2====
*Also known as Selenium Webdriver
*Supports WebDriver API thus providing maximum flexibility in porting the tests.
*Runs Selenium 1’s Selenium RC interface for backwards compatibility.

====Selenium Grid====
*Selenium-Grid allows the Selenium RC solution to scale for large test suites and for test suites that must be run in multiple environments.
*Selenium Grid runs the tests in parallel, that is, different tests can be run at the same time on different remote machines.
*Selenium Grid greatly improves the time it takes to run the suite by making use of parallel processing.

===Supported Browsers and Platforms===
====Selenium 2====
*Google Chrome 12.0.712.0+
*Internet Explorer 6, 7, 8, 9 - 32 and 64-bit where applicable
*Firefox 3.0, 3.5, 3.6, 4.0, 5.0, 6, 7
*Opera 11.5+
*HtmlUnit 2.9
*Android – 2.3+ for phones and tablets (devices & emulators)
*iOS 3+ for phones (devices & emulators) and 3.2+ for tablets (devices & emulators)

====Selenium 1 and Selenium IDE====
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Browser'''
| align="center" style="background:#f0f0f0;"|'''Selenium IDE'''
| align="center" style="background:#f0f0f0;"|'''Selenium 1 (RC)'''
| align="center" style="background:#f0f0f0;"|'''Operating Systems'''
|-
| Firefox 2, 3||Record and playback tests ||Start browser, run tests||Windows, Linux, Mac
|-
| IE 6, 7, 8||Unsupported ||Start browser, run tests||Windows
|-
| Safari 2, 3, 4||Unsupported ||Start browser, run tests||Windows, Mac
|-
| Opera 8, 9, 10||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
| Google Chrome||Unsupported ||Start browser, run tests||Windows, Linux, Mac
|-
|}

==Auto Hot Key==
AutoHotkey automates tests by sending keystrokes and mouse clicks to the target application with the help of a macro recorder.
Virtually any key, button, or combination can become a hotkey.
Following are the notable features of hotkey:
* Expand abbreviations as you type them. For example, typing "gn" can automatically produce "good night".
* Create custom data-entry forms, user interfaces, and menu bars.
* Remap keys and buttons on your keyboard, joystick, and mouse.
* Convert any script into an EXE file that can be run on computers that don't have AutoHotkey installed.

Quick start tutorial : http://www.autohotkey.com/docs/Tutorial.htm

==Watir==
Watir, pronounced water, stands for Web Application Testing in Ruby. Watir is an open-source (BSD) family of Ruby libraries for automating web browsers. It is distributed as a Ruby GEM named 'Watir'. Watir drives browsers the same way people do. It clicks links, fills in forms, presses buttons. Watir also checks results, such as whether expected text appears on the page or not.

There are 2 version available :
* Watir-Classic : supports only Internet Explorer on Windows
* Watir-WebDriver : supports Chrome, Firefox, Internet Explorer, Opera and also running in headless mode (HTMLUnit).

==GNU Xnee==
GNU Xnee is a suite of programs that can record, replay and distribute user actions under the X11 environment. Xnee has the capability to :
* Automate tests like nightly regression
* Demonstrate programs by recording and replaying a user interaction with the system
* Distribute actions from system admin to end users.

The Record and replay ‘macro’ is the highlight of Xnee.

==DOJO==
Dojo is a JavaScript framework targeting the many needs of large-scale client-side web development.

* Dojo abstracts the differences among diverse browsers to provide APIs that will work on all of them (it can even run on the server under Node.js)
* It establishes a framework for defining modules of code and managing their inter-dependencies
* Supports internationalization, localization, and accessibility
* Provides a rich suite of commonly needed utility classes and user-interface widgets.

==CubicTest==
CubicTest is a graphical Eclipse plug-in for writing Selenium and Watir tests. It makes tests faster and easier to write, and provides abstractions to make tests more robust and reusable.

* CubicTest's test editor is centered around pages/states and transitions between these pages/states.
* The model is intuitive for both Ajax and traditional web applications and supports most user interaction types.
* CubicTest features an innovative test recorder and test runner based on Selenium RC which are fully integrated with the graphical test editor.

==Dogtail==
Dogtail is a GUI test tool and automation framework written in Python. It uses Accessibility (a11y) technologies to communicate with desktop applications. Dogtail scripts are written in Python and executed like any other Python program.
Follwoing are the notable features of Dogtail:
* Object-Oriented API: With the object oriented API, you are under control of the UI tree and its elements, allowing you to write sophisticated scripts utilizing benefits of OO right deep from dogtail.
* Procedural API: Ace programmer credentials are not necessary to write useful automated scripts with procedural API.
* Easily Extensible: Writing custom classes and helper libraries are easy.
* Results and debug reporting: Separate logs for test case comparisons and debug information are generated.

==Sikuli==
Sikuli automates GUI testing by using image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code.
* Sikuli uses an innovative approach of automating GUI tests by using screenshots and powerpoint slides.
* Sikuli Script is a visual scripting API using Jython to create automation scripts.
* Sikuli includes an integrated development environment (IDE) for writing visual Sikuli scripts with screenshots.

==See Also==
==References==
*http://docs.seleniumhq.org/docs/
*http://www.eecs.yorku.ca/course_archive/2004-05/W/4313/Slides/Module10-GUI.pdf
*http://www.cs.helsinki.fi/u/paakki/mikkolainen.pdf
*http://watir.com/
*http://www.gnu.org/software/xnee/
*https://fedorahosted.org/dogtail/
*http://www.cubictest.org/
*http://www.autohotkey.com/
*http://www.sikuli.org/

==Note to reviewers==
The topic is very vast. Hence the wiki is written based on the guidelines provided by the TA's and the Prof.
* List all GUI tools used in OSS that you can quickly identify.
* Try to describe the tools to the same level of detail, except that you may choose to go into more detail on tools that are used with Rails.
* Listing of commands is not a good idea. You are not writing a reference manual; you are writing a descriptive article that someone might read to learn about what's available before choosing a tool or tools. You should aim for readability.

We have referred the respective tool websites to provide the overview for each one of them. We have provided appropriate citations as well. Additionally the tool and the documentation itself are under GNU/ open source licence and hence will not fall under copyright violation. Please correct us if we are wrong.

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-07T00:12:05Z

Vshesha: /* Selenium Grid */

==Introduction==
Graphical user interface testing is the process of testing a product's graphical user interface to ensure it meets its designed specifications.

GUI testing is difficult mainly due to following reasons :
* Large space of possibilities. Each sequence of GUI commands can result in various states. Evaluation of all these states is essential for validation of the GUI of the given software.
* Event-driven architecture. The test suite has to simulate the various user created actions.

Following are the challenges encountered while testing the graphical user interface of any software or system:
* Automation is difficult.
* The scope for testing is enormous
* Inability to determine the state of the program from GUI.
* Regression testing is difficult. Testcases may not be reusable

The current trend in user interfaces is geared towards graphical user interfaces (GUIs). This presents a problem for designing tests for software, since GUIs are very complex and hence GUI testing is very time consuming. Automation is a requirement for testing any larger graphical user interfaces, but automating GUI tests isn’t a straightforward task. Techniques which are familiar from the command line interface (CLI) age, don’t translate to the GUI world without problems.

==Test Automation==
The advantages of test automation are as follows.
*Frequent regression testing
*Rapid feedback to developers
*Virtually unlimited iterations of test case execution
*Support for Agile and extreme development methodologies
*Disciplined documentation of test cases
*Customized defect reporting
*Finding defects missed by manual testing

The challenge is in extending these advantages to GUI testing.

==GUI testing in Ruby==
==GUI Testing Tools==

GUI testing tools serve the purpose of automating the testing process of software with graphical user interfaces. Following are few of the available open source GUI testing tools:

*AutoHotkey
*CubicTest
*Dogtail
*Dojo
*Selenium
*Watir
*GNU Xnee
*Sikuli

==Selenium==

===Introduction===
Selenium is a portable software testing framework for web applications. Selenium provides a record/playback tool for authoring tests without learning a test scripting language (Selenium IDE). It also provides a test domain-specific language (Selenese) to write tests in a number of popular programming languages, including Java, C#, Groovy, Perl, PHP, Python and Ruby. The tests can then be run against most modern web browsers. Selenium deploys on Windows, Linux, and Macintosh platforms.

===Selenium Tool Suite===
Selenium is composed of multiple software tools.

====Selenium IDE====
*Prototyping tool for building testscripts.
*Firefox plugin provides easy to use interface for developing automated tests.
*Supports 'record and play' feature to create reusable scripts for testing.

====Selenium1====
*Also known as Selenium RC or Remote Control
*Provides flexibility in porting tests across browsers and platforms.
*Currently in maintainence mode. No active development.

====Selenium 2====
*Also known as Selenium Webdriver
*Supports WebDriver API thus providing maximum flexibility in porting the tests.
*Runs Selenium 1’s Selenium RC interface for backwards compatibility.

====Selenium Grid====
*Selenium-Grid allows the Selenium RC solution to scale for large test suites and for test suites that must be run in multiple environments.
*Selenium Grid runs the tests in parallel, that is, different tests can be run at the same time on different remote machines.
*Selenium Grid greatly improves the time it takes to run the suite by making use of parallel processing.

===Supported Browsers and Platforms===
====Selenium 2====
*Google Chrome 12.0.712.0+
*Internet Explorer 6, 7, 8, 9 - 32 and 64-bit where applicable
*Firefox 3.0, 3.5, 3.6, 4.0, 5.0, 6, 7
*Opera 11.5+
*HtmlUnit 2.9
*Android – 2.3+ for phones and tablets (devices & emulators)
*iOS 3+ for phones (devices & emulators) and 3.2+ for tablets (devices & emulators)

====Selenium 1 and Selenium IDE====
{| {{table}}
| align="center" style="background:#f0f0f0;"|'''Browser'''
| align="center" style="background:#f0f0f0;"|'''Selenium IDE'''
| align="center" style="background:#f0f0f0;"|'''Selenium 1 (RC)'''
| align="center" style="background:#f0f0f0;"|'''Operating Systems'''
|-
| Firefox 3.x||Record and playback tests||Start browser, run tests||Windows, Linux, Mac
|-
| Firefox 3||Record and playback tests||Start browser, run tests||Windows, Linux, Mac
|-
| Firefox 2||Record and playback tests||Start browser, run tests||Windows, Linux, Mac
|-
| IE 8||Test execution only via Selenium RC||Start browser, run tests||Windows
|-
| IE 7||Test execution only via Selenium RC||Start browser, run tests||Windows
|-
| IE 6||Test execution only via Selenium RC||Start browser, run tests||Windows
|-
| Safari 4||Test execution only via Selenium RC||Start browser, run tests||Windows, Mac
|-
| Safari 3||Test execution only via Selenium RC||Start browser, run tests||Windows, Mac
|-
| Safari 2||Test execution only via Selenium RC||Start browser, run tests||Windows, Mac
|-
| Opera 10||Test execution only via Selenium RC||Start browser, run tests||Windows, Linux, Mac
|-
| Opera 9||Test execution only via Selenium RC||Start browser, run tests||Windows, Linux, Mac
|-
| Opera 8||Test execution only via Selenium RC||Start browser, run tests||Windows, Linux, Mac
|-
| Google Chrome||Test execution only via Selenium RC||Start browser, run tests||Windows, Linux, Mac
|-
| Others||Test execution only via Selenium RC||Partial support possible**||As applicable
|}

==Auto Hot Key==
AutoHotkey automates tests by sending keystrokes and mouse clicks to the target application with the help of a macro recorder.
Virtually any key, button, or combination can become a hotkey.
Following are the notable features of hotkey:
* Expand abbreviations as you type them. For example, typing "gn" can automatically produce "good night".
* Create custom data-entry forms, user interfaces, and menu bars.
* Remap keys and buttons on your keyboard, joystick, and mouse.
* Convert any script into an EXE file that can be run on computers that don't have AutoHotkey installed.

Quick start tutorial : http://www.autohotkey.com/docs/Tutorial.htm

==Watir==
Watir, pronounced water, stands for Web Application Testing in Ruby. Watir is an open-source (BSD) family of Ruby libraries for automating web browsers. It is distributed as a Ruby GEM named 'Watir'. Watir drives browsers the same way people do. It clicks links, fills in forms, presses buttons. Watir also checks results, such as whether expected text appears on the page or not.

There are 2 version available :
* Watir-Classic : supports only Internet Explorer on Windows
* Watir-WebDriver : supports Chrome, Firefox, Internet Explorer, Opera and also running in headless mode (HTMLUnit).

==GNU Xnee==
GNU Xnee is a suite of programs that can record, replay and distribute user actions under the X11 environment. Xnee has the capability to :
* Automate tests like nightly regression
* Demonstrate programs by recording and replaying a user interaction with the system
* Distribute actions from system admin to end users.

The Record and replay ‘macro’ is the highlight of Xnee.

==DOJO==
Dojo is a JavaScript framework targeting the many needs of large-scale client-side web development.

* Dojo abstracts the differences among diverse browsers to provide APIs that will work on all of them (it can even run on the server under Node.js)
* It establishes a framework for defining modules of code and managing their inter-dependencies
* Supports internationalization, localization, and accessibility
* Provides a rich suite of commonly needed utility classes and user-interface widgets.

==CubicTest==
CubicTest is a graphical Eclipse plug-in for writing Selenium and Watir tests. It makes tests faster and easier to write, and provides abstractions to make tests more robust and reusable.

* CubicTest's test editor is centered around pages/states and transitions between these pages/states.
* The model is intuitive for both Ajax and traditional web applications and supports most user interaction types.
* CubicTest features an innovative test recorder and test runner based on Selenium RC which are fully integrated with the graphical test editor.

==Dogtail==
Dogtail is a GUI test tool and automation framework written in Python. It uses Accessibility (a11y) technologies to communicate with desktop applications. Dogtail scripts are written in Python and executed like any other Python program.
Follwoing are the notable features of Dogtail:
* Object-Oriented API: With the object oriented API, you are under control of the UI tree and its elements, allowing you to write sophisticated scripts utilizing benefits of OO right deep from dogtail.
* Procedural API: Ace programmer credentials are not necessary to write useful automated scripts with procedural API.
* Easily Extensible: Writing custom classes and helper libraries are easy.
* Results and debug reporting: Separate logs for test case comparisons and debug information are generated.

==Sikuli==
Sikuli automates GUI testing by using image recognition to identify and control GUI components. It is useful when there is no easy access to a GUI's internal or source code.
* Sikuli uses an innovative approach of automating GUI tests by using screenshots and powerpoint slides.
* Sikuli Script is a visual scripting API using Jython to create automation scripts.
* Sikuli includes an integrated development environment (IDE) for writing visual Sikuli scripts with screenshots.

==See Also==
==References==
*http://docs.seleniumhq.org/docs/
*http://www.eecs.yorku.ca/course_archive/2004-05/W/4313/Slides/Module10-GUI.pdf
*http://www.cs.helsinki.fi/u/paakki/mikkolainen.pdf
*http://watir.com/
*http://www.gnu.org/software/xnee/
*https://fedorahosted.org/dogtail/
*http://www.cubictest.org/
*http://www.autohotkey.com/
*http://www.sikuli.org/

==Note to reviewers==
The topic is very vast. Hence the wiki is written based on the guidelines provided by the TA's and the Prof.
* List all GUI tools used in OSS that you can quickly identify.
* Try to describe the tools to the same level of detail, except that you may choose to go into more detail on tools that are used with Rails.
* Listing of commands is not a good idea. You are not writing a reference manual; you are writing a descriptive article that someone might read to learn about what's available before choosing a tool or tools. You should aim for readability.

We have referred the respective tool websites to provide the overview for each one of them. We have provided appropriate citations as well. Additionally the tool and the documentation itself are under GNU/ open source licence and hence will not fall under copyright violation. Please correct us if we are wrong.

CSC/ECE 517 Fall 2013/ch1 1w32 av

2013-10-07T00:05:15Z

Vshesha: /* Selenium 2 */