Expertiza_Wiki - User contributions [en]

CSC/ECE 517 Fall 2014/final E1471 asuv

2014-11-12T04:43:13Z

Abora:

=Expertiza - Information Display and Student Interaction=

Expertiza is a web application developed using Ruby on Rails that serves as a peer-review system. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc)<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub]</ref><ref>[http://wikis.lib.ncsu.edu/index.php/Expertiza Expertiza Wiki Page]</ref>. It is an open source project and it's codebase is maintained in GitHub.

__TOC__

=Introduction=
Our contribution in this project would be to improve the display of questionnaires for all the instructors and also integrating a previous project which provides a new dashboard for students to view and compare their performance of each assignment.

==Current State==
*In the current state instructor should go through all the questionnaires to find the one they are looking for.
*The keyword search functionality is not yet implemented for questionnaires.
*The current student dashboard provides the average score and range of the student’s assignment, review and final score.
*The system has a limitation where in a student/instructor cannot view and compare the student scores based on the class performance.

==Goals==
*As a part of our project we will implement the search functionality and also make it possible to click and bring up a list of questionnaires used in the course, expanding only the applicable questionnaires in the list of questionnaires.
*A project from last year has the implementation for the new student dashboard. We would like to take that project, make the required changes to it and integrate it into expertiza.
*This new dashboard gives the students a comparative statistics for that particular assignment for the entire class.
*Giving the min, mean and max gives the student a range to judge where they stand with respect to the class.
*Other features were part of the project were to show the number of reviews and metareviews he/she has done for this assignment and also based on a threshold what are the number of reviews/metareviews the student still needs to do.
*A histogram distribution of the scores of the class (all teams) for that assignment would also shown as a part of the dashboard.

=Approach=

As the project was originally assigned to students two years ago, the functionality is mostly complete. The main concern is that, as the project was completed a significant amount of time ago (in December 2012), it was made for an older version of rails.

==General Approach==
Our general approach to the project would be as follows:
*Run the current project with rails 4
*Check the functionality to find out the incompatible and missing parts
*Refactor the parts of code that do not function as expected and port them to rails 4 specification
*After making sure everything runs, refactor the entire code to make sure it follows the global code rules.

==Specific Approach==
The specific approach to each of the two functionality is as follows:
===Better display for assignments===

We found that while the currently existing code covers most of the functionality, a major part of the functionality is missing. According to definition, the instructor should see the following on his home page:
*The instructor's courses
*Assignments for those courses
*Questionnaire by assignment name

Each of these should be compressed to titles only, and it should be possible to expand them by single mouse click. Each course should have its own list of assignments which can, again, be expanded. Also, there is a search box on the page which allows to search assignments, courses and questionnaires.

The search functionality for assignments and courses is working well, but the search for questionnaires is not implemented.

So, for this specific project, we plan to focus on implementing the search for questionnaires first. Then, integrate it all and test each functionality: make sure that nothing is affected by the new functionality added. After all the tests are performed, we will merge the project with the main project, thus integrating it with the final build.

===Dashboard for students===

The features required for the dashboard for students project have already been implemented. So, the main task to be performed by us is to merge the project files with the main project and make sure that nothing else is affected by the process.

The current code is able to display the maximum scores, average scores, number of reviews and distribution charts.

=Files involved=
===Files to be merged : Dashboard for students===
<ul>
<li>
Model
</li>
ScoreCache.rb
<li>
View
</li>
grades\view_my_scored.html.erb
<li>
Controller
</li>
grades_controller.rb, review_mapping_controller.rb,response_controller.rb
<li>
Database tables
</li>
Assignments,Participants, score_caches, response_maps,responses
</ul>

====Functionality of each file====

{| class="wikitable"
|-
! style="width:2%;"|Sr. No.
! style="width:8%;"|File Name
!style="width:13%;"| Type
! style="width:43%;"|Functionality involved for implementation
|- style="vertical-align:top;"
|-
|style="text-align:center;"|''''' 1 '''''
| <code> ScoreCache.rb </code>
| Model
| Makes an entry into score_cache table whenever a response is given/edited
|-
|style="text-align:center;"|''''' 2 '''''
| <code> grades\view_my_scores.html.erb </code>
| View
| Modified in order to display all new features
|-
|style="text-align:center;"|''''' 3 '''''
| <code> grades_controller.rb </code>
| Controller
| To get information all information about an assignment and its score which is average score of all reviews and plotting the graph for grade distinction
|-
|style="text-align:center;"|''''' 4 '''''
| <code> review_mapping_controller.rb </code>
| Controller
| To get additional information about assignment like total reviews submitted
|-
|style="text-align:center;"|''''' 5 '''''
| <code> Assignments </code>
| Table
| All information related to assignment
|-
|style="text-align:center;"|''''' 6 '''''
| <code> Responses </code>
| Table
| Stores individual assignment review response information
|-
|style="text-align:center;"|''''' 7 '''''
| <code> Score_caches </code>
| Table
| Stores individual assignment review score information
|-
|style="text-align:center;"|''''' 8 '''''
| <code> response_maps </code>
| Table
| Mapping between response, reviewer and reviewee
|}

===Files to be changed : Better display of assignment===
<ul>
<li>
Model
</li>
course_node.rb,assignment_node.rb,questionnaire_node.rb
<li>
View
</li>
tree_display\ _row_header.html.erb,tree_display\ _entry.html.erb,tree_display/actions/_courses_actions.html.erb
<li>
Controller
</li>
tree_display controller.rb,course_controller.rb,assignment_controller.rb,questionnaire_controller.rb
<li>
JavaScript
</li>
tableactions.js
</ul>

====Functionality of each file====

{| class="wikitable"
|-
! style="width:2%;"|Sr. No.
! style="width:8%;"|File Name
!style="width:13%;"| Type
! style="width:43%;"|Functionality involved for implementation
|- style="vertical-align:top;"
|-
|style="text-align:center;"|''''' 1 '''''
| <code> course_node.rb </code>
| Model
| To fetch information about all course none in the system
|-
|style="text-align:center;"|''''' 2 '''''
| <code> assignment_node.rb </code>
| Model
| To fetch information about all assignment node in the system
|-
|style="text-align:center;"|''''' 3 '''''
| <code> questionnaire_node.rb </code>
| Model
| To fetch information about all questionnaire node in the system
|-
|style="text-align:center;"|''''' 4 '''''
| <code> tree_display\ _row_header.html.erb </code>
| View
| Display of header in a row
|-
|style="text-align:center;"|''''' 5 '''''
| <code> tree_display\ _entry.html.erb </code>
| View
| Display entity in a row
|-
|style="text-align:center;"|''''' 6 '''''
| <code> tree_display/actions/_courses_actions.html.erb </code>
| View
| Display separate actions on each row
|-
|style="text-align:center;"|''''' 7 '''''
| <code> course_controller.rb </code>
| Controller
| Provides various course related functions
|-
|style="text-align:center;"|''''' 8 '''''
| <code> assignment_controller.rb </code>
| Controller
| Provides various assignment related functions
|-
|style="text-align:center;"|''''' 9 '''''
| <code> questionnaire_controller.rb </code>
| Controller
| Provides various questionnaire related functions
|-
|style="text-align:center;"|''''' 10 '''''
| <code> tree_display controller.rb </code>
| Controller
| For direct access to every entity like questionnaires, review rubric etc..
|}

=Use case=
For the instructor, there needs to be a way to quickly find rubrics (and other questionnaires) that have been used in a single course. It should be possible to search or click somewhere to bring up a list of questionnaires used in the course, expanding only the applicable questionnaires in the list of questionnaires. A search functionality for questionnaire is expected. Currently, assignment and course searches is implemented, and there is a dropdown for questionnaire, but it's functionality is missing.

'''Actor:''' Instructot

'''Other Participants:''' None

'''Precondition:''' There are few questionnaires in the system

'''Primary Sequence:'''

1. Log in to Expertiza

2. Instructor lands on "Manage content" page

3. Search for a questionnaire, by selecting questionnaire in the search dropdown and input some search string

4. Search results displayed, expanding only the applicable questionnaires in the list of questionnaires

[[File:Assignment_display_existing.jpg]]

The following use case diagram shows the system of Assignment grades for a student on Expertiza as it is depicted right now. These include viewing their own project submission (with url and attachments), reviews and metareviews on their work, author feedbacks, teammate reviews and their final score on that assignment/project.<ref>Previous year's design document for ''E715: Dashboard for Students'' by Ambika Tripathi, Milan Tonse, Krutika Nagar, Shruti Buch</ref> As part of this project we shall be adding more data on this page, so that student has better understanding of his/her marks.

'''Name''': Students viewing scores for the assignment

'''Actor''': Student

'''Other Participants''': None

'''Precondition''': Statistics have been recorded for average high and low scores.

'''Primary Sequence:'''

1. Log in to Expertiza

2. Select an assignment

3. Select Your Scores

4. Click on the link for view class scores for this assignment.

5. View the average, high and low class score for that particular assignment

'''Name''': Students viewing graphical output for scores for the assignment

'''Actor''': Student

'''Other Participants''': None

'''Precondition''': Statistics have been recorded for average high and low scores.

'''Primary Sequence:'''

1. Log in to Expertiza

2. Select an assignment

3. Select Your Scores

4. Click on the link for view class scores for this assignment.

5. View the graphical output for average, high and low class score for that particular assignment

'''Name''': Students viewing number of reviews done by him/her

'''Actor''': Student

'''Other Participants:''' None

'''Precondition''': Statistics have been recorded for number of reviews done by the student.

'''Primary Sequence:'''

1. Log in to Expertiza

2. Select an assignment

3. Select Your Scores

4. Click on the link for my reviews for this assignment.

5. View the number of reviews the student has done for that particular assignment and also the

number of reviews he still has to do to reach the threshold.

'''Name''': Students viewing number of metareviews done by him/her

'''Actor''': Student

'''Other Participants:''' None

'''Precondition''': Statistics have been recorded for number of metareviews done by the student.

'''Primary Sequence:'''

1. Log in to Expertiza

2. Select an assignment

3. Select Your Scores

4. Click on the link for my metareviews for this assignment.

5. View the number of metareviews the student has done for that particular assignment and also

the number of metareviews he still has to do to reach the threshold.

'''Name''': Students viewing average number of class reviews for the assignment

'''Actor''': Student

'''Other Participants:''' None

'''Precondition''': Statistics have been recorded for class reviews for that assignment.

'''Primary Sequence:'''

1. Log in to Expertiza

2. Select an assignment

3. Select Your Scores

4. Click on the link for view class reviews for this assignment.

5. View the average number of class reviews for that particular assignment

'''Name''': Students viewing average number of class metareviews for the assignment

'''Actor''': Student

'''Other Participants:''' None

'''Precondition''': Statistics have been recorded for class metareviews for that assignment.

'''Primary Sequence:'''

1. Log in to Expertiza

2. Select an assignment

3. Select Your Scores

4. Click on the link for view class metareviews for this assignment.

5. View the average number of class metareviews for that particular assignment

[[File:Dashboard_existing.jpg]]

[[File:Dashboard_new.jpg]]
=UML diagram=
Following is class diagram for Assignment display module. <ref>Previous year's design document for ''E707: Better display for assignments'' by Bharath Sampath(bsampat2),Prakash Vasudevan(pvasude),Raghavendran Nedunchezhian(rnedunc), Yuchuan Liu(yliu63)</ref>

[[File:UML.jpg]]

Following is class diagram for Dashboard for students module.

[[File:Dashboard.jpg]]

='''References'''=
<references/>

CSC/ECE 517 Fall 2014/final E1471 asuv

2014-11-12T04:38:28Z

Abora:

=Expertiza - Information Display and Student Interaction=

Expertiza is a web application developed using Ruby on Rails that serves as a peer-review system. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc)<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub]</ref><ref>[http://wikis.lib.ncsu.edu/index.php/Expertiza Expertiza Wiki Page]</ref>. It is an open source project and it's codebase is maintained in GitHub.

__TOC__

=Introduction=
Our contribution in this project would be to improve the display of questionnaires for all the instructors and also integrating a previous project which provides a new dashboard for students to view and compare their performance of each assignment.

==Current State==
*In the current state instructor should go through all the questionnaires to find the one they are looking for.
*The keyword search functionality is not yet implemented for questionnaires.
*The current student dashboard provides the average score and range of the student’s assignment, review and final score.
*The system has a limitation where in a student/instructor cannot view and compare the student scores based on the class performance.

==Goals==
*As a part of our project we will implement the search functionality and also make it possible to click and bring up a list of questionnaires used in the course, expanding only the applicable questionnaires in the list of questionnaires.
*A project from last year has the implementation for the new student dashboard. We would like to take that project, make the required changes to it and integrate it into expertiza.
*This new dashboard gives the students a comparative statistics for that particular assignment for the entire class.
*Giving the min, mean and max gives the student a range to judge where they stand with respect to the class.
*Other features were part of the project were to show the number of reviews and metareviews he/she has done for this assignment and also based on a threshold what are the number of reviews/metareviews the student still needs to do.
*A histogram distribution of the scores of the class (all teams) for that assignment would also shown as a part of the dashboard.

=Approach=

As the project was originally assigned to students two years ago, the functionality is mostly complete. The main concern is that, as the project was completed a significant amount of time ago (in December 2012), it was made for an older version of rails.

==General Approach==
Our general approach to the project would be as follows:
*Run the current project with rails 4
*Check the functionality to find out the incompatible and missing parts
*Refactor the parts of code that do not function as expected and port them to rails 4 specification
*After making sure everything runs, refactor the entire code to make sure it follows the global code rules.

==Specific Approach==
The specific approach to each of the two functionality is as follows:
===Better display for assignments===

We found that while the currently existing code covers most of the functionality, a major part of the functionality is missing. According to definition, the instructor should see the following on his home page:
*The instructor's courses
*Assignments for those courses
*Questionnaire by assignment name

Each of these should be compressed to titles only, and it should be possible to expand them by single mouse click. Each course should have its own list of assignments which can, again, be expanded. Also, there is a search box on the page which allows to search assignments, courses and questionnaires.

The search functionality for assignments and courses is working well, but the search for questionnaires is not implemented.

So, for this specific project, we plan to focus on implementing the search for questionnaires first. Then, integrate it all and test each functionality: make sure that nothing is affected by the new functionality added. After all the tests are performed, we will merge the project with the main project, thus integrating it with the final build.

===Dashboard for students===

The features required for the dashboard for students project have already been implemented. So, the main task to be performed by us is to merge the project files with the main project and make sure that nothing else is affected by the process.

The current code is able to display the maximum scores, average scores, number of reviews and distribution charts.

=Files involved=
===Files to be merged : Dashboard for students===
<ul>
<li>
Model
</li>
ScoreCache.rb
<li>
View
</li>
grades\view_my_scored.html.erb
<li>
Controller
</li>
grades_controller.rb, review_mapping_controller.rb,response_controller.rb
<li>
Database tables
</li>
Assignments,Participants, score_caches, response_maps,responses
</ul>

====Functionality of each file====

{| class="wikitable"
|-
! style="width:2%;"|Sr. No.
! style="width:8%;"|File Name
!style="width:13%;"| Type
! style="width:43%;"|Functionality involved for implementation
|- style="vertical-align:top;"
|-
|style="text-align:center;"|''''' 1 '''''
| <code> ScoreCache.rb </code>
| Model
| Makes an entry into score_cache table whenever a response is given/edited
|-
|style="text-align:center;"|''''' 2 '''''
| <code> grades\view_my_scores.html.erb </code>
| View
| Modified in order to display all new features
|-
|style="text-align:center;"|''''' 3 '''''
| <code> grades_controller.rb </code>
| Controller
| To get information all information about an assignment and its score which is average score of all reviews and plotting the graph for grade distinction
|-
|style="text-align:center;"|''''' 4 '''''
| <code> review_mapping_controller.rb </code>
| Controller
| To get additional information about assignment like total reviews submitted
|-
|style="text-align:center;"|''''' 5 '''''
| <code> Assignments </code>
| Table
| All information related to assignment
|-
|style="text-align:center;"|''''' 6 '''''
| <code> Responses </code>
| Table
| Stores individual assignment review response information
|-
|style="text-align:center;"|''''' 7 '''''
| <code> Score_caches </code>
| Table
| Stores individual assignment review score information
|-
|style="text-align:center;"|''''' 8 '''''
| <code> response_maps </code>
| Table
| Mapping between response, reviewer and reviewee
|}

===Files to be changed : Better display of assignment===
<ul>
<li>
Model
</li>
course_node.rb,assignment_node.rb,questionnaire_node.rb
<li>
View
</li>
tree_display\ _row_header.html.erb,tree_display\ _entry.html.erb,tree_display/actions/_courses_actions.html.erb
<li>
Controller
</li>
tree_display controller.rb,course_controller.rb,assignment_controller.rb,questionnaire_controller.rb
<li>
JavaScript
</li>
tableactions.js
</ul>

====Functionality of each file====

{| class="wikitable"
|-
! style="width:2%;"|Sr. No.
! style="width:8%;"|File Name
!style="width:13%;"| Type
! style="width:43%;"|Functionality involved for implementation
|- style="vertical-align:top;"
|-
|style="text-align:center;"|''''' 1 '''''
| <code> course_node.rb </code>
| Model
| To fetch information about all course none in the system
|-
|style="text-align:center;"|''''' 2 '''''
| <code> assignment_node.rb </code>
| Model
| To fetch information about all assignment node in the system
|-
|style="text-align:center;"|''''' 3 '''''
| <code> questionnaire_node.rb </code>
| Model
| To fetch information about all questionnaire node in the system
|-
|style="text-align:center;"|''''' 4 '''''
| <code> tree_display\ _row_header.html.erb </code>
| View
| Display of header in a row
|-
|style="text-align:center;"|''''' 5 '''''
| <code> tree_display\ _entry.html.erb </code>
| View
| Display entity in a row
|-
|style="text-align:center;"|''''' 6 '''''
| <code> tree_display/actions/_courses_actions.html.erb </code>
| View
| Display separate actions on each row
|-
|style="text-align:center;"|''''' 7 '''''
| <code> course_controller.rb </code>
| Controller
| Provides various course related functions
|-
|style="text-align:center;"|''''' 8 '''''
| <code> assignment_controller.rb </code>
| Controller
| Provides various assignment related functions
|-
|style="text-align:center;"|''''' 9 '''''
| <code> questionnaire_controller.rb </code>
| Controller
| Provides various questionnaire related functions
|-
|style="text-align:center;"|''''' 10 '''''
| <code> tree_display controller.rb </code>
| Controller
| For direct access to every entity like questionnaires, review rubric etc..
|}

=Use case=
For the instructor, there needs to be a way to quickly find rubrics (and other questionnaires) that have been used in a single course. It should be possible to search or click somewhere to bring up a list of questionnaires used in the course, expanding only the applicable questionnaires in the list of questionnaires. A search functionality for questionnaire is expected. Currently, assignment and course searches is implemented, and there is a dropdown for questionnaire, but it's functionality is missing.

'''Actor:''' Instructot

'''Other Participants:''' None

'''Precondition:''' There are few questionnaires in the system

'''Primary Sequence:'''

1. Log in to Expertiza

2. Instructor lands on "Manage content" page

3. Search for a questionnaire, by selecting questionnaire in the search dropdown and input some search string

4. Search results displayed, expanding only the applicable questionnaires in the list of questionnaires

[[File:Assignment_display_existing.jpg]]

The following use case diagram shows the system of Assignment grades for a student on Expertiza as it is depicted right now. These include viewing their own project submission (with url and attachments), reviews and metareviews on their work, author feedbacks, teammate reviews and their final score on that assignment/project.<ref>Previous year's design document for ''E715: Dashboard for Students'' by Ambika Tripathi, Milan Tonse, Krutika Nagar, Shruti Buch</ref> As part of this project we shall be adding more data on this page, so that student has better understanding of his/her marks.

'''Name''': Students viewing scores for the assignment

'''Actor''': Student

'''Other Participants''': None

'''Precondition''': Statistics have been recorded for average high and low scores.

'''Primary Sequence:'''

1. Log in to Expertiza

2. Select an assignment

3. Select Your Scores

4. Click on the link for view class scores for this assignment.

5. View the average, high and low class score for that particular assignment

'''Name''': Students viewing graphical output for scores for the assignment

'''Actor''': Student

'''Other Participants''': None

'''Precondition''': Statistics have been recorded for average high and low scores.

'''Primary Sequence:'''

1. Log in to Expertiza

2. Select an assignment

3. Select Your Scores

4. Click on the link for view class scores for this assignment.

5. View the graphical output for average, high and low class score for that particular assignment

'''Name''': Students viewing number of reviews done by him/her

'''Actor''': Student

'''Other Participants:''' None

'''Precondition''': Statistics have been recorded for number of reviews done by the student.

'''Primary Sequence:'''

1. Log in to Expertiza

2. Select an assignment

3. Select Your Scores

4. Click on the link for my reviews for this assignment.

5. View the number of reviews the student has done for that particular assignment and also the

number of reviews he still has to do to reach the threshold.

'''Name''': Students viewing number of metareviews done by him/her

'''Actor''': Student

'''Other Participants:''' None

'''Precondition''': Statistics have been recorded for number of metareviews done by the student.

'''Primary Sequence:'''

1. Log in to Expertiza

2. Select an assignment

3. Select Your Scores

4. Click on the link for my metareviews for this assignment.

5. View the number of metareviews the student has done for that particular assignment and also

the number of metareviews he still has to do to reach the threshold.

'''Name''': Students viewing average number of class reviews for the assignment

'''Actor''': Student

'''Other Participants:''' None

'''Precondition''': Statistics have been recorded for class reviews for that assignment.

'''Primary Sequence:'''

1. Log in to Expertiza

2. Select an assignment

3. Select Your Scores

4. Click on the link for view class reviews for this assignment.

5. View the average number of class reviews for that particular assignment

'''Name''': Students viewing average number of class metareviews for the assignment

'''Actor''': Student

'''Other Participants:''' None

'''Precondition''': Statistics have been recorded for class metareviews for that assignment.

'''Primary Sequence:'''

1. Log in to Expertiza

2. Select an assignment

3. Select Your Scores

4. Click on the link for view class metareviews for this assignment.

5. View the average number of class metareviews for that particular assignment

[[File:Dashboard_existing.jpg]]

[[File:Dashboard_new.jpg]]
=UML diagram=
[[File:UML.jpg]]

[[File:Dashboard.jpg]]

='''References'''=
<references/>

File:Dashboard.jpg

2014-11-12T04:37:10Z

Abora:

CSC/ECE 517 Fall 2014/final E1471 asuv

2014-11-12T03:42:25Z

Abora:

=Expertiza - Information Display and Student Interaction=

Expertiza is a web application developed using Ruby on Rails that serves as a peer-review system. The application allows students to submit and peer-review learning objects (articles, code, web sites, etc)<ref>[https://github.com/expertiza/expertiza Expertiza on GitHub]</ref><ref>[http://wikis.lib.ncsu.edu/index.php/Expertiza Expertiza Wiki Page]</ref>. It is an open source project and it's codebase is maintained in GitHub.

__TOC__

=Introduction=
Our contribution in this project would be to improve the display of questionnaires for all the instructors and also integrating a previous project which provides a new dashboard for students to view and compare their performance of each assignment.

==Current State==
*In the current state instructor should go through all the questionnaires to find the one they are looking for.
*The keyword search functionality is not yet implemented for questionnaires.
*The current student dashboard provides the average score and range of the student’s assignment, review and final score.
*The system has a limitation where in a student/instructor cannot view and compare the student scores based on the class performance.

==Goals==
*As a part of our project we will implement the search functionality and also make it possible to click and bring up a list of questionnaires used in the course, expanding only the applicable questionnaires in the list of questionnaires.
*A project from last year has the implementation for the new student dashboard. We would like to take that project, make the required changes to it and integrate it into expertiza.
*This new dashboard gives the students a comparative statistics for that particular assignment for the entire class.
*Giving the min, mean and max gives the student a range to judge where they stand with respect to the class.
*Other features were part of the project were to show the number of reviews and metareviews he/she has done for this assignment and also based on a threshold what are the number of reviews/metareviews the student still needs to do.
*A histogram distribution of the scores of the class (all teams) for that assignment would also shown as a part of the dashboard.

=Approach=

As the project was originally assigned to students two years ago, the functionality is mostly complete. The main concern is that, as the project was completed a significant amount of time ago (in December 2012), it was made for an older version of rails.

==General Approach==
Our general approach to the project would be as follows:
*Run the current project with rails 4
*Check the functionality to find out the incompatible and missing parts
*Refactor the parts of code that do not function as expected and port them to rails 4 specification
*After making sure everything runs, refactor the entire code to make sure it follows the global code rules.

==Specific Approach==
The specific approach to each of the two functionality is as follows:
===Better display for assignments===

We found that while the currently existing code covers most of the functionality, a major part of the functionality is missing. According to definition, the instructor should see the following on his home page:
*The instructor's courses
*Assignments for those courses
*Questionnaire by assignment name

Each of these should be compressed to titles only, and it should be possible to expand them by single mouse click. Each course should have its own list of assignments which can, again, be expanded. Also, there is a search box on the page which allows to search assignments, courses and questionnaires.

The search functionality for assignments and courses is working well, but the search for questionnaires is not implemented.

So, for this specific project, we plan to focus on implementing the search for questionnaires first. Then, integrate it all and test each functionality: make sure that nothing is affected by the new functionality added. After all the tests are performed, we will merge the project with the main project, thus integrating it with the final build.

===Dashboard for students===

The features required for the dashboard for students project have already been implemented. So, the main task to be performed by us is to merge the project files with the main project and make sure that nothing else is affected by the process.

The current code is able to display the maximum scores, average scores, number of reviews and distribution charts.

=Files involved=
===Files to be merged : Dashboard for students===
<ul>
<li>
Model
</li>
ScoreCache.rb
<li>
View
</li>
grades\view_my_scored.html.erb
<li>
Controller
</li>
grades_controller.rb, review_mapping_controller.rb,response_controller.rb
<li>
Database tables
</li>
Assignments,Participants, score_caches, response_maps,responses
</ul>

====Functionality of each file====

{| class="wikitable"
|-
! style="width:2%;"|Sr. No.
! style="width:8%;"|File Name
!style="width:13%;"| Type
! style="width:43%;"|Functionality for this project
|- style="vertical-align:top;"
|-
|style="text-align:center;"|''''' 1 '''''
| <code> ScoreCache.rb </code>
| Model
| Makes an entry into score_cache table whenever a response is given/edited
|-
|style="text-align:center;"|''''' 2 '''''
| <code> grades\view_my_scores.html.erb </code>
| View
| Modified in order to display all new features
|-
|style="text-align:center;"|''''' 3 '''''
| <code> grades_controller.rb </code>
| Controller
| To get information all information about an assignment and its score which is average score of all reviews and plotting the graph for grade distinction
|-
|style="text-align:center;"|''''' 4 '''''
| <code> review_mapping_controller.rb </code>
| Controller
| To get additional information about assignment like total reviews submitted
|-
|style="text-align:center;"|''''' 5 '''''
| <code> Assignments </code>
| Table
| All information related to assignment
|-
|style="text-align:center;"|''''' 6 '''''
| <code> Responses </code>
| Table
| Stores individual assignment review response information
|-
|style="text-align:center;"|''''' 7 '''''
| <code> Score_caches </code>
| Table
| Stores individual assignment review score information
|-
|style="text-align:center;"|''''' 8 '''''
| <code> response_maps </code>
| Table
| Mapping between response, reviewer and reviewee
|}

===Files to be changed : Better display of assignment===
<ul>
<li>
Model
</li>
course_node.rb,assignment_node.rb,questionnaire_node.rb
<li>
View
</li>
tree_display\ _row_header.html.erb,tree_display\ _entry.html.erb,tree_display/actions/_courses_actions.html.erb
<li>
Controller
</li>
tree_display controller.rb,course_controller.rb,assignment_controller.rb,questionnaire_controller.rb
<li>
JavaScript
</li>
tableactions.js
</ul>

====Functionality of each file====

{| class="wikitable"
|-
! style="width:2%;"|Sr. No.
! style="width:8%;"|File Name
!style="width:13%;"| Type
! style="width:43%;"|Functionality for this project
|- style="vertical-align:top;"
|-
|style="text-align:center;"|''''' 1 '''''
| <code> course_node.rb </code>
| Model
| To fetch information about all course none in the system
|-
|style="text-align:center;"|''''' 2 '''''
| <code> assignment_node.rb </code>
| Model
| To fetch information about all assignment node in the system
|-
|style="text-align:center;"|''''' 3 '''''
| <code> questionnaire_node.rb </code>
| Model
| To fetch information about all questionnaire node in the system
|-
|style="text-align:center;"|''''' 4 '''''
| <code> tree_display controller.rb </code>
| Controller
| For direct access to every entity like questionnaires, review rubric etc..
|-
|style="text-align:center;"|''''' 5 '''''
| <code> tree_display\ _row_header.html.erb </code>
| View
| Display of header in a row
|-
|style="text-align:center;"|''''' 6 '''''
| <code> tree_display\ _entry.html.erb </code>
| View
| Display entity in a row
|-
|style="text-align:center;"|''''' 7 '''''
| <code> tree_display/actions/_courses_actions.html.erb </code>
| View
| Display separate actions on each row
|-
|style="text-align:center;"|''''' 8 '''''
| <code> course_controller.rb </code>
| Controller
| Provides various course related functions
|-
|style="text-align:center;"|''''' 9 '''''
| <code> assignment_controller.rb </code>
| Controller
| Provides various assignment related functions
|-
|style="text-align:center;"|''''' 10 '''''
| <code> questionnaire_controller.rb </code>
| Controller
| Provides various questionnaire related functions

|}

=Use case=
For the instructor, there needs to be a way to quickly find rubrics (and other questionnaires) that have been used in a single course. It should be possible to search or click somewhere to bring up a list of questionnaires used in the course, expanding only the applicable questionnaires in the list of questionnaires. A search functionality for questionnaire is expected. Currently, assignment and course searches is implemented, and there is a dropdown for questionnaire, but it's functionality is missing.

'''Actor:''' Instructot

'''Other Participants:''' None

'''Precondition:''' There are few questionnaires in the system

'''Primary Sequence:'''

1. Log in to Expertiza

2. Instructor lands on "Manage content" page

3. Search for a questionnaire, by selecting questionnaire in the search dropdown and input some search string

4. Search results displayed, expanding only the applicable questionnaires in the list of questionnaires

[[File:Assignment_display_existing.jpg]]

The following use case diagram shows the system of Assignment grades for a student on Expertiza as it is depicted right now. These include viewing their own project submission (with url and attachments), reviews and metareviews on their work, author feedbacks, teammate reviews and their final score on that assignment/project.<ref>Previous year's design document for ''E715: Dashboard for Students'' by Ambika Tripathi, Milan Tonse, Krutika Nagar, Shruti Buch</ref> As part of this project we shall be adding more data on this page, so that student has better understanding of his/her marks.

'''Name''': Students viewing scores for the assignment

'''Actor''': Student

'''Other Participants''': None

'''Precondition''': Statistics have been recorded for average high and low scores.

'''Primary Sequence:'''

1. Log in to Expertiza

2. Select an assignment

3. Select Your Scores

4. Click on the link for view class scores for this assignment.

5. View the average, high and low class score for that particular assignment

'''Name''': Students viewing graphical output for scores for the assignment

'''Actor''': Student

'''Other Participants''': None

'''Precondition''': Statistics have been recorded for average high and low scores.

'''Primary Sequence:'''

1. Log in to Expertiza

2. Select an assignment

3. Select Your Scores

4. Click on the link for view class scores for this assignment.

5. View the graphical output for average, high and low class score for that particular assignment

'''Name''': Students viewing number of reviews done by him/her

'''Actor''': Student

'''Other Participants:''' None

'''Precondition''': Statistics have been recorded for number of reviews done by the student.

'''Primary Sequence:'''

1. Log in to Expertiza

2. Select an assignment

3. Select Your Scores

4. Click on the link for my reviews for this assignment.

5. View the number of reviews the student has done for that particular assignment and also the

number of reviews he still has to do to reach the threshold.

'''Name''': Students viewing number of metareviews done by him/her

'''Actor''': Student

'''Other Participants:''' None

'''Precondition''': Statistics have been recorded for number of metareviews done by the student.

'''Primary Sequence:'''

1. Log in to Expertiza

2. Select an assignment

3. Select Your Scores

4. Click on the link for my metareviews for this assignment.

5. View the number of metareviews the student has done for that particular assignment and also

the number of metareviews he still has to do to reach the threshold.

'''Name''': Students viewing average number of class reviews for the assignment

'''Actor''': Student

'''Other Participants:''' None

'''Precondition''': Statistics have been recorded for class reviews for that assignment.

'''Primary Sequence:'''

1. Log in to Expertiza

2. Select an assignment

3. Select Your Scores

4. Click on the link for view class reviews for this assignment.

5. View the average number of class reviews for that particular assignment

'''Name''': Students viewing average number of class metareviews for the assignment

'''Actor''': Student

'''Other Participants:''' None

'''Precondition''': Statistics have been recorded for class metareviews for that assignment.

'''Primary Sequence:'''

1. Log in to Expertiza

2. Select an assignment

3. Select Your Scores

4. Click on the link for view class metareviews for this assignment.

5. View the average number of class metareviews for that particular assignment

[[File:Dashboard_existing.jpg]]

[[File:Dashboard_new.jpg]]
=UML diagram=
[[File:UML.jpg]]

='''References'''=
<references/>

CSC/ECE 517 Fall 2014/final E1471 asuv

2014-11-11T22:03:42Z

Abora:

File:UML.jpg

2014-11-11T21:55:45Z

Abora: uploaded a new version of "File:UML.jpg"

File:Dashboard existing.jpg

2014-11-11T21:40:04Z

Abora: uploaded a new version of "File:Dashboard existing.jpg"

CSC/ECE 517 Fall 2014/final E1471 asuv

2014-11-11T21:34:01Z

Abora:

CSC/ECE 517 Fall 2014/final E1471 asuv

2014-11-11T21:33:24Z

Abora:

File:Dashboard existing.jpg

2014-11-11T21:29:16Z

Abora: uploaded a new version of "File:Dashboard existing.jpg"

File:Dashboard new.jpg

2014-11-11T21:15:33Z

Abora:

File:Dashboard existing.jpg

2014-11-11T21:15:17Z

Abora:

File:Assignment display existing.jpg

2014-11-11T21:14:46Z

Abora:

CSC/ECE 517 Fall 2014/final E1471 asuv

2014-11-11T19:33:12Z

Abora:

CSC/ECE 517 Fall 2014/oss E1457 ags

2014-10-28T03:02:25Z

Abora:

=Expertiza - Refactoring DynamicReviewMapping Controller=

__TOC__

==Introduction==
It is time consuming to assess project work in a large classroom environment, and one of the best techniques to achieve this is to have students assist in this assessment. If each student is asked to assess a few (say, one to five) other students or student teams, the task requires a reasonable amount of effort; and that effort does not increase as the class gets larger. "''Expertiza is a system for managing all kinds of communication that is involved in assessment: double-blind communications between authors and reviewers, assessment of teammate contributions, evaluations by course staff, and surveys of students to assess the assignment and the
peer-review process.''" <ref>http://www.igi-global.com/book/monitoring-assessment-online-collaborative-environments/773&f=e-book</ref>
''"Expertiza project uses peer review to create reusable learning objects.''"<ref>http://expertiza.ncsu.edu/</ref> Students select from a list of tasks to be performed, with several students selecting each task. Then they prepare their work and submit it to an electronic peer-review system. The work is then reviewed by other students, who offer comments to help the submitters improve their work. The best submissions for each task are then selected for use in later courses. Expertiza gets students working together to improve others’ learning experiences. It helps them learn, by making them think through the lecture material and apply it to a real-world situation, just as they might do in an on-the-job situation. These learning objects can be improved iteratively; for example, the next year’s class can be presented with the examples developed by students the previous year, and asked to identify shortcomings and develop improved examples.<ref>http://scholar.google.com/scholar?q=%22Reusable+learning+objects+through+peer+review%3A+The+Expertiza+approach%22+%22The+Expertiza+platform+is+a+divide-and-conquer%22&btnG=&hl=en&as_sdt=0%2C34</ref> More information on Expertiza can be found [https://github.com/expertiza/expertiza here].

==Refactoring in Ruby==
Refactoring helps to<ref>http://www.refactoringinruby.com/</ref>
*Understand what led to poor code design
*Fix code which is difficult to understand
*Express each idea “once and only once”
*Recognize missing or inadequately formed classes
*Simplify overly complex relationships between classes
*Achieve the right balance of responsibilities among objects
*Make code easier to test and more maintainable

===Refactoring Techniques===
There are many documented refactoring techniques, and a few common ones are below.<ref>http://www.integralist.co.uk/posts/refactoring-techniques/</ref>
*'''Rename Method''': Renaming identifiers can reduce the need for code comments and nearly always helps to promote greater clarity.
*'''Introduce Explaining Variable''': So here is a technique specifically based around the premise of renaming.
For example:
<pre>
unless "This is a String with some CAPS".scan(/([A-Z])/).empty?
puts "capitalised text was found"
end
</pre>
Should be:
<pre>
caps_not_found = "This is a String with some CAPS".scan(/([A-Z])/).empty?

unless caps_not_found
puts "capitalised text was found"
end
</pre>

*'''Extract Method''': It consists of breaking up long methods by shifting overly complex chunks of code into new methods which have very descriptive identifiers.
For example:
<pre>
class Foo
attr_reader :bar

def initialize bar
@bar = bar
end

def do_something
puts "my baz" # notice this is duplication
puts bar
end

def do_something_else
puts "my baz" # notice this is duplication
puts "Something else"
puts bar
end
end
</pre>

Becomes:
<pre>
class Foo
attr_reader :bar

def initialize bar
@bar = bar
end

def do_something
baz
puts bar
end

def do_something_else
baz
puts "Something else"
puts bar
end

def baz
puts "my baz"
end
end
</pre>

*'''Inline Method''': Sometimes you want the opposite of the Extract Method technique. Imagine a method exists whose content is already simple and clear, and whose identifier adds no extra benefit. So to fix this problem we'll convert the method invocation into an inlined piece of code.

*'''Pull Up Method''': When you have duplicated code across two separate classes then the best refactoring technique to implement is to pull that duplicate code up into a super class so we DRY (Don't Repeat Yourself) out the code and allow it to be used in multiple places without duplication (meaning changes in future only have to happen in one place).

For example:
<pre>
class Person
attr_reader :first_name, :last_name

def initialize first_name, last_name
@first_name = first_name
@last_name = last_name
end

end

class MalePerson < Person
# This is duplicated in the `FemalePerson` class
def full_name
first_name + " " + last_name
end

def gender
"M"
end
end

class FemalePerson < Person
# This is duplicated in the `MalePerson` class
def full_name
first_name + " " + last_name
end

def gender
"F"
end
end
</pre>
Becomes:
<pre>
class Person
attr_reader :first_name, :last_name

def initialize first_name, last_name
@first_name = first_name
@last_name = last_name
end

def full_name
first_name + " " + last_name
end
end

class MalePerson < Person
def gender
"M"
end
end

class FemalePerson < Person
def gender
"F"
end
end
</pre>

*'''Introduce Named Parameter''':When method arguments are unclear then convert them into named parameters so they become clearer (and easier to remember).

==Project Description==

==Modification to Existing Code==

==Further Reading==
*[http://www.refactoringinruby.com/ Refactoring In Ruby]
*[http://refactoring.com/ Refactoring]

==References==
<references/><br>

CSC/ECE 517 Fall 2014/oss E1457 ags

2014-10-28T02:57:48Z

Abora:

=Expertiza - Refactoring DynamicReviewMapping Controller=

__TOC__

==Introduction==
It is time consuming to assess project work in a large classroom environment, and one of the best techniques to achieve this is to have students assist in this assessment. If each student is asked to assess a few (say, one to five) other students or student teams, the task requires a reasonable amount of effort; and that effort does not increase as the class gets larger. "''Expertiza is a system for managing all kinds of communication that is involved in assessment: double-blind communications between authors and reviewers, assessment of teammate contributions, evaluations by course staff, and surveys of students to assess the assignment and the
peer-review process.''" <ref>http://www.igi-global.com/book/monitoring-assessment-online-collaborative-environments/773&f=e-book</ref>
''"Expertiza project uses peer review to create reusable learning objects.''"<ref>http://expertiza.ncsu.edu/</ref> Students select from a list of tasks to be performed, with several students selecting each task. Then they prepare their work and submit it to an electronic peer-review system. The work is then reviewed by other students, who offer comments to help the submitters improve their work. The best submissions for each task are then selected for use in later courses. Expertiza gets students working together to improve others’ learning experiences. It helps them learn, by making them think through the lecture material and apply it to a real-world situation, just as they might do in an on-the-job situation. These learning objects can be improved iteratively; for example, the next year’s class can be presented with the examples developed by students the previous year, and asked to identify shortcomings and develop improved examples.<ref>http://scholar.google.com/scholar?q=%22Reusable+learning+objects+through+peer+review%3A+The+Expertiza+approach%22+%22The+Expertiza+platform+is+a+divide-and-conquer%22&btnG=&hl=en&as_sdt=0%2C34</ref> More information on Expertiza can be found [https://github.com/expertiza/expertiza here].

==Refactoring in Ruby==
Refactoring helps to<ref>http://www.refactoringinruby.com/</ref>
*Understand what led to poor code design
*Fix code which is difficult to understand
*Express each idea “once and only once”
*Recognize missing or inadequately formed classes
*Simplify overly complex relationships between classes
*Achieve the right balance of responsibilities among objects
*Make code easier to test and more maintainable

===Refactoring Techniques===
There are many documented refactoring techniques, and a few common ones are below.<ref>http://www.integralist.co.uk/posts/refactoring-techniques/</ref>
*'''Rename Method''': Renaming identifiers can reduce the need for code comments and nearly always helps to promote greater clarity.
*'''Introduce Explaining Variable''': So here is a technique specifically based around the premise of renaming.
For example:
<pre>
unless "This is a String with some CAPS".scan(/([A-Z])/).empty?
puts "capitalised text was found"
end
</pre>
Should be:
<pre>
caps_not_found = "This is a String with some CAPS".scan(/([A-Z])/).empty?

unless caps_not_found
puts "capitalised text was found"
end
</pre>

*'''Extract Method''': It consists of breaking up long methods by shifting overly complex chunks of code into new methods which have very descriptive identifiers.
For example:
<pre>
class Foo
attr_reader :bar

def initialize bar
@bar = bar
end

def do_something
puts "my baz" # notice this is duplication
puts bar
end

def do_something_else
puts "my baz" # notice this is duplication
puts "Something else"
puts bar
end
end
</pre>

Becomes:
<pre>
class Foo
attr_reader :bar

def initialize bar
@bar = bar
end

def do_something
baz
puts bar
end

def do_something_else
baz
puts "Something else"
puts bar
end

def baz
puts "my baz"
end
end
</pre>

*'''Inline Method''': Sometimes you want the opposite of the Extract Method technique. Imagine a method exists whose content is already simple and clear, and whose identifier adds no extra benefit. So to fix this problem we'll convert the method invocation into an inlined piece of code.

*'''Pull Up Method''': When you have duplicated code across two separate classes then the best refactoring technique to implement is to pull that duplicate code up into a super class so we DRY (Don't Repeat Yourself) out the code and allow it to be used in multiple places without duplication (meaning changes in future only have to happen in one place).

For example:
<pre>
class Person
attr_reader :first_name, :last_name

def initialize first_name, last_name
@first_name = first_name
@last_name = last_name
end

end

class MalePerson < Person
# This is duplicated in the `FemalePerson` class
def full_name
first_name + " " + last_name
end

def gender
"M"
end
end

class FemalePerson < Person
# This is duplicated in the `MalePerson` class
def full_name
first_name + " " + last_name
end

def gender
"F"
end
end
</pre>
Becomes:
<pre>
class Person
attr_reader :first_name, :last_name

def initialize first_name, last_name
@first_name = first_name
@last_name = last_name
end

def full_name
first_name + " " + last_name
end
end

class MalePerson < Person
def gender
"M"
end
end

class FemalePerson < Person
def gender
"F"
end
end
</pre>

*'''Introduce Named Parameter''':When method arguments are unclear then convert them into named parameters so they become clearer (and easier to remember).

==Project Description==

==Further Reading==
*[http://www.refactoringinruby.com/ Refactoring In Ruby]
*[http://refactoring.com/ Refactoring]

==References==
<references/><br>

CSC/ECE 517 Fall 2014/oss E1457 ags

2014-10-28T01:28:59Z

Abora:

CSC/ECE 517 Fall 2014/oss E1457 ags

2014-10-28T00:28:27Z

Abora: Created page with "=Expertiza - Refactoring DynamicReviewMapping Controller= __TOC__ ==Introduction== ==Project Description== ==References== <references/><br>"

=Expertiza - Refactoring DynamicReviewMapping Controller=

__TOC__

==Introduction==

==Project Description==

==References==
<references/><br>

CSC/ECE 517 Fall 2014/ch1a 22 as

2014-09-25T09:45:00Z

Abora:

'''HP Unified Functional Testing Professional'''

''"'''HP Unified Functional Testing (UFT)''' software, previously known as '''HP Quick Test Professional (QTP)''',<ref>http://www.automationrepository.com/2012/12/hp-unified-functional-testing-uft-11-5-new-features</ref> provides [http://en.wikipedia.org/wiki/Functional_testing functional testing] and [http://en.wikipedia.org/wiki/Regression_testing regression testing] automation for software applications.<ref>http://www8.hp.com/us/en/software-solutions/application-lifecycle-management-application-test-software/index.html?zn=bto&cp=1-11-127-24^1352_4000_1__</ref> HP Unified Functional Testing can be used for enterprise [http://en.wikipedia.org/wiki/Quality_assurance quality assurance].<ref>http://www.learnqtp.com/qtp-quality-center-test-director-guide/</ref>"'' HP Unified Functional Testing is a test automation tool originally developed by [http://en.wikipedia.org/wiki/Mercury_Interactive Mercury Interactive] and later acquired by [http://en.wikipedia.org/wiki/Hewlett-Packard Hewlett Packard].<ref> http://www.devbistro.com/articles/Testing/Mercury-QuickTest-Professional-Evaluation</ref> HP Unified Functional Testing 11.5 combined HP QuickTest Professional and HP Service Test into a single software package,<ref> http://selftechy.com/2013/10/07/hp-uft-11-50-unified-functional-testing</ref> which is currently available from the HP Software Division. The integrated HP Unified Functional Testing software allows developers to test from a single console all three layers of a program’s operations: the interface, [http://en.wikipedia.org/wiki/Service_layer the service layer] and the database layer.<ref>http://www.computerworld.com/article/2493313/data-center/hp-simplifies-automated-software-testing-suite.html</ref>

[https://docs.google.com/document/d/1eq3XHiUUBIrEBx-R2Mgolaw7HttSgzPniwDLEF5oVk0/edit# Writeup page.]
{| align=right style="border: 1px solid gray;" class="wikitable"
|+ HP Uniffied Functional Testing<ref>http://en.wikipedia.org/wiki/HP_QuickTest_Professional</ref>
|-
| [http://en.wikipedia.org/wiki/Software_developer? Developer(s)] || [http://en.wikipedia.org/wiki/Hewlett-Packard? HP], [http://en.wikipedia.org/wiki/HP_Software_Division? HP Software Division]
|-
| [http://en.wikipedia.org/wiki/Software_release_life_cycle? Stable release] || 12.01
|-
| [http://en.wikipedia.org/wiki/Operating_system? Operating system] || [http://en.wikipedia.org/wiki/Microsoft_Windows? Microsoft Windows]
|-
| [http://en.wikipedia.org/wiki/List_of_software_categories? Type] || [http://en.wikipedia.org/wiki/Test_automation? Test automation tools]
|-
| [http://en.wikipedia.org/wiki/Software_license? License] || [http://en.wikipedia.org/wiki/Proprietary_software? Proprietary]
|}

=='''Background'''==
Test automation is the use of software to control the execution of tests cases, the comparison of actual to predicted results, the setting up of test preconditions, and other test control and test reporting functions.<ref>''The Testing Network, An Integral Approach to Test Activities in Large Software Projects'' by Jean-Jacques Pierre Henry (Aug 17, 2008), p413, ISBN 978-3-540-78504-0</ref> Test Automation is a development discipline as it uses scripting languages to instruct the tool how to interact with your application. As such careful consideration needs to be paid to

* Exception handling for bugs that occur during testing cycles(i.e, unexpected error messages during a test run).
* How the tool synchronizes with your application(e.g. if there are slow response times from your environment)
* The level of maintenance required to keep the tests up to date with changes in the application [http://en.wikipedia.org/wiki/Graphical_user_interface GUI](i.e, new buttons, data fields, custom controls etc)

Any test automation framework is a set of assumptions, concepts and tools that provide support for automating the major activities in the testing process. The main advantage of a framework is

* Increased Productivity
* Easy and Reduced maintenance effort
* Consistent automation development across projects
* Process driven than person driven approach
* Controlled maintenance of automation artifacts

There is a range of automation testing tools available. Some of them are licensed and few others are open sourced. QTP, Cucumber, Capybara and other tools<ref>http://en.wikipedia.org/wiki/List_of_web_testing_tools</ref>

=='''Description'''==
HP UFT is generally used for GUI based Test Case Automation, it can also automate some non-GUI based test cases like database testing, webservice testing and file based operations. It offers a graphical user interface, keyboard support, multiple testing views, and scripting language.
<ref>http://www.softwaretestinghelp.com/qtp-quicktest-professional-tutorial-1/</ref>
===Data Driven Testing===
HP Unified Functional Testing allows us to perform data-driven testing. For example, data can be output to a data table for reuse. [http://en.wikipedia.org/wiki/Data-driven_testing Data-driven testing] is implemented as a Microsoft Excel workbook, which is accessible from HP Unified Functional Testing. HP Unified Functional Testing has two data tables: the Global data sheet and Action (local) data sheets. The test steps can read data from these data tables in order to drive variable data into the application under test, and verify the expected result.<ref>http://www.qtp10.com/2009/07/using-global-and-action-data-sheets-in.html</ref>

===Views===
HP Unified Functional Testing provides two views—and ways to modify—a test script: Keyword View and Expert View. These views enable HP Unified Functional Testing to act as an Integrated Development Environment (IDE) for the test, and HP Unified Functional Testing includes many standard IDE features, such as breakpoints to pause a test at predetermined places.<ref>http://en.wikipedia.org/wiki/HP_QuickTest_Professional</ref>

====Keyword view====
Keyword View lets users create and view the steps of a test in a modular, table format. In Keyword View, users can also view properties for items such as checkpoints, output values, and actions, use conditional and loop statements, and insert breakpoints to assist in debugging a test.<ref>http://www.qtp10.com/2009/07/working-with-keyword-view-in-hp-qtp.html</ref>

====Expert View====
Expert view displays test code using [http://en.wikipedia.org/wiki/VBScript VBScript]. Designed for more advanced users, users can edit all test actions except for the root Global action, and changes are synchronized with the Keyword View.<ref>http://www.fdscallcentre.com/homepage/data/mi/DS-0413-020_QTPro6.0.pdf</ref>

===Scripting===
HP UFT's VBScript allows for classes, but not other object oriented properties such as inheritance and polymorphism. It also lacks a debugger, however UFT has a debugger provided by HP. Some Windows script ([http://en.wikipedia.org/wiki/Windows_Script_Host WScript],[http://en.wikipedia.org/wiki/WSH WSH],[http://en.wikipedia.org/wiki/Wmii WMI]) & [http://en.wikipedia.org/wiki/Visual_Basic_.NET VB.Net] code can be used in a script in the expert view <ref>https://h20546.www2.hp.com/main/training/course_details.cfm?Course=00008165&sitepick=US</ref>

===Types of testing===
UFT typically supports following types of testing:

1. Regression testing

2. Unit testing

3. Load testing

4. Integration testing

5. Functional testing

6. Regression testing

7. Acceptance testing

8. Performance testing

9. Stress testing

Further reading on [http://www.softwaretestinghelp.com/types-of-software-testing/ testing types]

===Example===
QTP script for opening a Notepad file<ref>http://kuldeepse.wordpress.com/2007/11/11/qtp-script-for-sending-a-mail-using-outlook/</ref>.
<pre>invokeapplication”c:/whatever the path”
Run
Dim a
Set a = WScript.CreateObject (“WSCript.shell”)
a.run “notepad.exe”

Dim oShell
Set oShell = CreateObject (“WSCript.shell”)
oShell.run “cmd/notepad.exe”
Set oShell = Nothing

DsystemUtil.Run “Notepad.exe”
</pre>
===Exception handling===
Application crashes, Unexpected events and errors during a run session can interrupt the run session and mislead results. This is a problem particularly when tests run unattended—the test pauses until one performs the operation needed to recover. To handle these situations, Exception Handling and Error handling is must while developing script or Automation Framework.<ref>http://qtpautomationcodes.blogspot.com/2013/05/error-handling-in-qtp.html</ref>
Error and Exception handling in HP UFT can be done by any of the following ways:

* [http://www.softwaretestinghelp.com/conditional-loop-statements-qtp-tutorial-4/ Conditional Statement]
* [http://www.tutorialspoint.com/qtp/qtp_error_handling.htm On Error statement]
* [http://www.tutorialspoint.com/qtp/qtp_recovery_scenarios.htm Recovery Scenarios]

=='''Life Cycle'''==
A typical [http://www.learnqtp.com/forums/Thread-Automation-Life-Cycle life cycle] of HP UFT looks like this.

[[File:LifeCycle.jpg‎]]

=='''Comparison to other tools'''==
Tools like [http://en.wikipedia.org/wiki/Cucumber_(software) Cucumber] and [http://rubygems.org/gems/capybara Capybara] run tests from the viewpoint of the user. Cucumber translates user stories into tests and Capybara simulates a user or web browser. Unified Functional Testing is used by programmers to preform specific test cases they code themselves.<ref>''Engineering Long-Lasting Software: An Agile Approach Using SaaS and Cloud Computing'', Beta Edition 0.9.0 by Armando Fox and David Patterson, August 23, 2012, p136, </ref>

'''Capybara''' talks to a website, just like a human would do (example: visit a url, click on the specific area of the sceen, input data and submit the form). It imitates user flow over website. Test cases in Capybara will look like this:<ref>http://stackoverflow.com/questions/15004918/cucumber-vs-capybara</ref>
<pre>
describe "the signup process", :type => :feature do
before :each do
User.make(:email => 'user@example.com', :password => 'caplin')
end
it "signs me in" do
visit '/sessions/new'
within("#session") do
fill_in 'Login', :with => 'user@example.com'
fill_in 'Password', :with => 'password'
end
click_link 'Sign in'
page.should have_content 'Success'
end
end</pre>

'''Cucumber''' tests are very much human readable. Example:<ref>http://stackoverflow.com/questions/15004918/cucumber-vs-capybara</ref>

<pre>
Scenario: Signup process
Given a user exists with email "user@example.com" and password "caplin"
When I try to login with "user@example.com" and "caplin"
Then I should be logged in successfully
</pre>

[http://en.wikipedia.org/wiki/Selenium Selenium] is a tool for automating web applications for testing purposes.

'''Comparison of UFT with other tools'''<ref>http://www.aspiresys.com/WhitePapers/QTPvsSelenium.pdf</ref><ref>http://www.qtphelp.com/2011/06/advantages-and-disadvantages-of-qtp.html</ref>
{| border="1" class="wikitable"
|+
! Feature
! UFT
! Selenium
! Cucumber/ Capybara
|-
! Windows (Non-browser)
based Application support
| Yes
| No
| No
|-
! Environment Support
| Only Windows
| Windows , Linux , Solaris
OS X , Others
| Windows , Linux , Solaris
OS X , Others
|-
! Windows (Non-browser)
based Application support
| Yes
| No
| No
|-
!Software Cost
| License & Annual maintenance Fees
| Zero
| Zero
|-
!Coding Experience of
Engineer
|Not Much
|Should be very good along with
technical capabilities of integrating
different pieces of framework
|Requires minimal use of Ruby programming
|-
!Script written in
|VBScript
|Java, Ruby, Python, C#, and PHP
|Ruby
|-
!Script Creation Time
|Low
|High
|Medium
|-
|-
!Multiple threads/instances
|Not supported
|Supported, we can run multiple instances of the
application on different browsers at the same time
|Supported, we can run multiple instances of the
application on different browsers at the same time
|-
!Hardware resource (CPU
+ RAM) consumption during
script execution
|High
|Low
|Low
|-
!Product Support
|Dedicate HP support along with
support forums
|Open Source Community
|Open Source Community
|-
!Framework
|Easily integrated with [http://en.wikipedia.org/wiki/HP_Quality_Center HP Quality Center] or [http://en.wikipedia.org/wiki/HP_Application_Lifecycle_Management HP ALM]
|Selenium + Eclipse + [http://en.wikipedia.org/wiki/MAVEN Maven] / [http://en.wikipedia.org/wiki/Apache_Ant ANT]
+[http://en.wikipedia.org/wiki/Jenkins_(software) Jenkins] / [http://en.wikipedia.org/wiki/Hudson_(software) Hudson] & its plugins /
Cruise Control + [http://en.wikipedia.org/wiki/TestNG TestNG] + [http://en.wikipedia.org/wiki/Apache_Subversion SVN]
|Ruby on Rails
[http://en.wikipedia.org/wiki/Merb Merb]

[http://en.wikipedia.org/wiki/Sinatra_(software) Sinatra]
|-
!Continuous Integration
|Possible through Quality Center
/ ALM or Jenkins
|Possible through Jenkins / Hudson
/ Cruise Control
|Possible through Rake, Ant, Maven and [http://en.wikipedia.org/wiki/JUnit JUnit] output
|}

=='''Advantages'''==
1. Support for different addins like Java, Oracle, SAP, .NET, Web Forms, Siebel, PeopleSoft, Web services, Main frame (Terminal Emulator) etc.

2. UFT comes with an inbuilt IDE

3. UFT can be integrated with Test management tools like QC (Quality Center)

4. Easy to maintain test iterations and data driving the tests through configurations

5.''' Record and Playback:''' It is pretty easy even for a non-programmer to record scripts / test cases, customize / modify and play back the tests

=='''Disadvantages'''==
UFT popularity is slowly shrinking.<ref>http://www.quora.com/Is-there-demand-for-QTP</ref> It is being used more for legacy applications.

People are moving away from UFT because of it's reactive approach of writing test automation. Testers write the scripts. With cucumber, capybara and selenium, automation test are joint effort between developers and the testers. The testers write the test cases in cucumber scenario format, then the developers write the steps definition. This way, everyone is contributing and everyone is reviewing the test cases.<ref>http://qastuffs.blogspot.com/2010_12_01_archive.html</ref>

=='''References'''==
<references/>

CSC/ECE 517 Fall 2014/ch1a 22 as

2014-09-25T09:37:05Z

Abora:

'''HP Unified Functional Testing Professional'''

''"'''HP Unified Functional Testing (UFT)''' software, previously known as '''HP Quick Test Professional (QTP)''',<ref>http://www.automationrepository.com/2012/12/hp-unified-functional-testing-uft-11-5-new-features</ref> provides [http://en.wikipedia.org/wiki/Functional_testing functional testing] and [http://en.wikipedia.org/wiki/Regression_testing regression testing] automation for software applications.<ref>http://www8.hp.com/us/en/software-solutions/application-lifecycle-management-application-test-software/index.html?zn=bto&cp=1-11-127-24^1352_4000_1__</ref> HP Unified Functional Testing can be used for enterprise [http://en.wikipedia.org/wiki/Quality_assurance quality assurance].<ref>http://www.learnqtp.com/qtp-quality-center-test-director-guide/</ref>"'' HP Unified Functional Testing is a test automation tool originally developed by [http://en.wikipedia.org/wiki/Mercury_Interactive Mercury Interactive] and later acquired by [http://en.wikipedia.org/wiki/Hewlett-Packard Hewlett Packard].<ref> http://www.devbistro.com/articles/Testing/Mercury-QuickTest-Professional-Evaluation</ref> HP Unified Functional Testing 11.5 combined HP QuickTest Professional and HP Service Test into a single software package,<ref> http://selftechy.com/2013/10/07/hp-uft-11-50-unified-functional-testing</ref> which is currently available from the HP Software Division. The integrated HP Unified Functional Testing software allows developers to test from a single console all three layers of a program’s operations: the interface, [http://en.wikipedia.org/wiki/Service_layer the service layer] and the database layer.<ref>http://www.computerworld.com/article/2493313/data-center/hp-simplifies-automated-software-testing-suite.html</ref>

[https://docs.google.com/document/d/1eq3XHiUUBIrEBx-R2Mgolaw7HttSgzPniwDLEF5oVk0/edit# Writeup page.]
{| align=right style="border: 1px solid gray;" class="wikitable"
|+ HP Uniffied Functional Testing<ref>http://en.wikipedia.org/wiki/HP_QuickTest_Professional</ref>
|-
| [http://en.wikipedia.org/wiki/Software_developer? Developer(s)] || [http://en.wikipedia.org/wiki/Hewlett-Packard? HP], [http://en.wikipedia.org/wiki/HP_Software_Division? HP Software Division]
|-
| [http://en.wikipedia.org/wiki/Software_release_life_cycle? Stable release] || 12.01
|-
| [http://en.wikipedia.org/wiki/Operating_system? Operating system] || [http://en.wikipedia.org/wiki/Microsoft_Windows? Microsoft Windows]
|-
| [http://en.wikipedia.org/wiki/List_of_software_categories? Type] || [http://en.wikipedia.org/wiki/Test_automation? Test automation tools]
|-
| [http://en.wikipedia.org/wiki/Software_license? License] || [http://en.wikipedia.org/wiki/Proprietary_software? Proprietary]
|}

=='''Background'''==
Test automation is the use of software to control the execution of tests cases, the comparison of actual to predicted results, the setting up of test preconditions, and other test control and test reporting functions.<ref>''The Testing Network, An Integral Approach to Test Activities in Large Software Projects'' by Jean-Jacques Pierre Henry (Aug 17, 2008), p413, ISBN 978-3-540-78504-0</ref> Test Automation is a development discipline as it uses scripting languages to instruct the tool how to interact with your application. As such careful consideration needs to be paid to

* Exception handling for bugs that occur during testing cycles(i.e, unexpected error messages during a test run).
* How the tool synchronizes with your application(e.g. if there are slow response times from your environment)
* The level of maintenance required to keep the tests up to date with changes in the application [http://en.wikipedia.org/wiki/Graphical_user_interface GUI](i.e, new buttons, data fields, custom controls etc)

Any test automation framework is a set of assumptions, concepts and tools that provide support for automating the major activities in the testing process. The main advantage of a framework is

* Increased Productivity
* Easy and Reduced maintenance effort
* Consistent automation development across projects
* Process driven than person driven approach
* Controlled maintenance of automation artifacts

There is a range of automation testing tools available. Some of them are licensed and few others are open sourced. QTP, Cucumber, Capybara and other tools<ref>http://en.wikipedia.org/wiki/List_of_web_testing_tools</ref>

=='''Description'''==
HP UFT is generally used for GUI based Test Case Automation, it can also automate some non-GUI based test cases like database testing, webservice testing and file based operations. It offers a graphical user interface, keyboard support, multiple testing views, and scripting language.
<ref>http://www.softwaretestinghelp.com/qtp-quicktest-professional-tutorial-1/</ref>
===Data Driven Testing===
HP Unified Functional Testing allows us to perform data-driven testing. For example, data can be output to a data table for reuse. [http://en.wikipedia.org/wiki/Data-driven_testing Data-driven testing] is implemented as a Microsoft Excel workbook, which is accessible from HP Unified Functional Testing. HP Unified Functional Testing has two data tables: the Global data sheet and Action (local) data sheets. The test steps can read data from these data tables in order to drive variable data into the application under test, and verify the expected result.<ref>http://www.qtp10.com/2009/07/using-global-and-action-data-sheets-in.html</ref>

===Views===
HP Unified Functional Testing provides two views—and ways to modify—a test script: Keyword View and Expert View. These views enable HP Unified Functional Testing to act as an Integrated Development Environment (IDE) for the test, and HP Unified Functional Testing includes many standard IDE features, such as breakpoints to pause a test at predetermined places.<ref>http://en.wikipedia.org/wiki/HP_QuickTest_Professional</ref>

====Keyword view====
Keyword View lets users create and view the steps of a test in a modular, table format. In Keyword View, users can also view properties for items such as checkpoints, output values, and actions, use conditional and loop statements, and insert breakpoints to assist in debugging a test.<ref>http://www.qtp10.com/2009/07/working-with-keyword-view-in-hp-qtp.html</ref>

====Expert View====
Expert view displays test code using [http://en.wikipedia.org/wiki/VBScript VBScript]. Designed for more advanced users, users can edit all test actions except for the root Global action, and changes are synchronized with the Keyword View.<ref>http://www.fdscallcentre.com/homepage/data/mi/DS-0413-020_QTPro6.0.pdf</ref>

===Scripting===
HP UFT's VBScript allows for classes, but not other object oriented properties such as inheritance and polymorphism. It also lacks a debugger, however UFT has a debugger provided by HP. Some Windows script ([http://en.wikipedia.org/wiki/Windows_Script_Host WScript],[http://en.wikipedia.org/wiki/WSH WSH],[http://en.wikipedia.org/wiki/Wmii WMI]) & [http://en.wikipedia.org/wiki/Visual_Basic_.NET VB.Net] code can be used in a script in the expert view <ref>https://h20546.www2.hp.com/main/training/course_details.cfm?Course=00008165&sitepick=US</ref>

===Types of testing===
UFT typically supports following types of testing:

1. Regression testing

2. Unit testing

3. Load testing

4. Integration testing

5. Functional testing

6. Regression testing

7. Acceptance testing

8. Performance testing

9. Stress testing

Further reading on [http://www.softwaretestinghelp.com/types-of-software-testing/ testing types]

===Example===
QTP script for opening a Notepad file<ref>http://kuldeepse.wordpress.com/2007/11/11/qtp-script-for-sending-a-mail-using-outlook/</ref>.
<pre>invokeapplication”c:/whatever the path”
Run
Dim a
Set a = WScript.CreateObject (“WSCript.shell”)
a.run “notepad.exe”

Dim oShell
Set oShell = CreateObject (“WSCript.shell”)
oShell.run “cmd/notepad.exe”
Set oShell = Nothing

DsystemUtil.Run “Notepad.exe”
</pre>
===Exception handling===
Application crashes, Unexpected events and errors during a run session can interrupt the run session and mislead results. This is a problem particularly when tests run unattended—the test pauses until one performs the operation needed to recover. To handle these situations, Exception Handling and Error handling is must while developing script or Automation Framework.<ref>http://qtpautomationcodes.blogspot.com/2013/05/error-handling-in-qtp.html</ref>
Error and Exception handling in HP UFT can be done by any of the following ways:

* [http://www.softwaretestinghelp.com/conditional-loop-statements-qtp-tutorial-4/ Conditional Statement]
* [http://www.tutorialspoint.com/qtp/qtp_error_handling.htm On Error statement]
* [http://www.tutorialspoint.com/qtp/qtp_recovery_scenarios.htm Recovery Scenarios]

=='''Life Cycle'''==
A typical [http://www.learnqtp.com/forums/Thread-Automation-Life-Cycle life cycle] of HP UFT looks like this.

[[File:LifeCycle.jpg‎]]

=='''Comparison to other tools'''==
Tools like [http://en.wikipedia.org/wiki/Cucumber_(software) Cucumber] and [http://rubygems.org/gems/capybara Capybara] run tests from the viewpoint of the user. Cucumber translates user stories into tests and Capybara simulates a user or web browser. Unified Functional Testing is used by programmers to preform specific test cases they code themselves.<ref>''Engineering Long-Lasting Software: An Agile Approach Using SaaS and Cloud Computing'', Beta Edition 0.9.0 by Armando Fox and David Patterson, August 23, 2012, p136, </ref>

'''Capybara''' talks to a website, just like a human would do (example: visit a url, click on the specific area of the sceen, input data and submit the form). It imitates user flow over website. Test cases in Capybara will look like this:<ref>http://stackoverflow.com/questions/15004918/cucumber-vs-capybara</ref>
<pre>
describe "the signup process", :type => :feature do
before :each do
User.make(:email => 'user@example.com', :password => 'caplin')
end
it "signs me in" do
visit '/sessions/new'
within("#session") do
fill_in 'Login', :with => 'user@example.com'
fill_in 'Password', :with => 'password'
end
click_link 'Sign in'
page.should have_content 'Success'
end
end</pre>

'''Cucumber''' tests are very much human readable. Example:<ref>http://stackoverflow.com/questions/15004918/cucumber-vs-capybara</ref>

<pre>
Scenario: Signup process
Given a user exists with email "user@example.com" and password "caplin"
When I try to login with "user@example.com" and "caplin"
Then I should be logged in successfully
</pre>

[http://en.wikipedia.org/wiki/Selenium Selenium] is a tool for automating web applications for testing purposes.

'''Comparison of UFT with other tools'''<ref>http://www.aspiresys.com/WhitePapers/QTPvsSelenium.pdf</ref><ref>http://www.qtphelp.com/2011/06/advantages-and-disadvantages-of-qtp.html</ref>
{| border="1" class="wikitable"
|+
! Feature
! UFT
! Selenium
! Cucumber/ Capybara
|-
! Windows (Non-browser)
based Application support
| Yes
| No
| No
|-
! Environment Support
| Only Windows
| Windows , Linux , Solaris
OS X , Others
| Windows , Linux , Solaris
OS X , Others
|-
! Windows (Non-browser)
based Application support
| Yes
| No
| No
|-
!Software Cost
| License & Annual maintenance Fees
| Zero
| Zero
|-
!Coding Experience of
Engineer
|Not Much
|Should be very good along with
technical capabilities of integrating
different pieces of framework
|Requires minimal use of Ruby programming
|-
!Script written in
|VBScript
|Java, Ruby, Python, C#, and PHP
|Ruby
|-
!Script Creation Time
|Low
|High
|Medium
|-
|-
!Multiple threads/instances
|Not supported
|Supported, we can run multiple instances of the
application on different browsers at the same time
|Supported, we can run multiple instances of the
application on different browsers at the same time
|-
!Hardware resource (CPU
+ RAM) consumption during
script execution
|High
|Low
|Low
|-
!Product Support
|Dedicate HP support along with
support forums
|Open Source Community
|Open Source Community
|-
!Framework
|Easily integrated with [http://en.wikipedia.org/wiki/HP_Quality_Center HP Quality Center] or [http://en.wikipedia.org/wiki/HP_Application_Lifecycle_Management HP ALM]
|Selenium + Eclipse + [http://en.wikipedia.org/wiki/MAVEN Maven] / [http://en.wikipedia.org/wiki/Apache_Ant ANT]
+[http://en.wikipedia.org/wiki/Jenkins_(software) Jenkins] / [http://en.wikipedia.org/wiki/Hudson_(software) Hudson] & its plugins /
Cruise Control + [http://en.wikipedia.org/wiki/TestNG TestNG] + [http://en.wikipedia.org/wiki/Apache_Subversion SVN]
|Ruby on Rails
[http://en.wikipedia.org/wiki/Merb Merb]

[http://en.wikipedia.org/wiki/Sinatra_(software) Sinatra]
|-
!Continuous Integration
|Possible through Quality Center
/ ALM or Jenkins
|Possible through Jenkins / Hudson
/ Cruise Control
|Possible through Rake, Ant, Maven and [http://en.wikipedia.org/wiki/JUnit JUnit] output
|}

=='''Disadvantages'''==
UFT popularity is slowly shrinking.<ref>http://www.quora.com/Is-there-demand-for-QTP</ref> It is being used more for legacy applications.

People are moving away from UFT because of it's reactive approach of writing test automation. Testers write the scripts. With cucumber, capybara and selenium, automation test are joint effort between developers and the testers. The testers write the test cases in cucumber scenario format, then the developers write the steps definition. This way, everyone is contributing and everyone is reviewing the test cases.<ref>http://qastuffs.blogspot.com/2010_12_01_archive.html</ref>

=='''References'''==
<references/>

CSC/ECE 517 Fall 2014/ch1a 22 as

2014-09-25T09:04:19Z

Abora:

'''HP Unified Functional Testing Professional'''

'''HP Unified Functional Testing (UFT)''' software, previously known as '''HP Quick Test Professional (QTP)''',<ref>http://www.automationrepository.com/2012/12/hp-unified-functional-testing-uft-11-5-new-features</ref> provides [http://en.wikipedia.org/wiki/Functional_testing functional testing] and [http://en.wikipedia.org/wiki/Regression_testing regression testing] automation for software applications.<ref>http://www8.hp.com/us/en/software-solutions/application-lifecycle-management-application-test-software/index.html?zn=bto&cp=1-11-127-24^1352_4000_1__</ref> HP Unified Functional Testing can be used for enterprise [http://en.wikipedia.org/wiki/Quality_assurance quality assurance].<ref>http://www.learnqtp.com/qtp-quality-center-test-director-guide/</ref> HP Unified Functional Testing is a test automation tool originally developed by [http://en.wikipedia.org/wiki/Mercury_Interactive Mercury Interactive] and later acquired by [http://en.wikipedia.org/wiki/Hewlett-Packard Hewlett Packard].<ref> http://www.devbistro.com/articles/Testing/Mercury-QuickTest-Professional-Evaluation</ref> HP Unified Functional Testing 11.5 combined HP QuickTest Professional and HP Service Test into a single software package,<ref> http://selftechy.com/2013/10/07/hp-uft-11-50-unified-functional-testing</ref> which is currently available from the HP Software Division. The integrated HP Unified Functional Testing software allows developers to test from a single console all three layers of a program’s operations: the interface, [http://en.wikipedia.org/wiki/Service_layer the service layer] and the database layer.<ref>http://www.computerworld.com/article/2493313/data-center/hp-simplifies-automated-software-testing-suite.html</ref>

[https://docs.google.com/document/d/1eq3XHiUUBIrEBx-R2Mgolaw7HttSgzPniwDLEF5oVk0/edit# Writeup page.]
{| align=right style="border: 1px solid gray;" class="wikitable"
|+ HP Uniffied Functional Testing<ref>http://en.wikipedia.org/wiki/HP_QuickTest_Professional</ref>
|-
| [http://en.wikipedia.org/wiki/Software_developer? Developer(s)] || [http://en.wikipedia.org/wiki/Hewlett-Packard? HP], [http://en.wikipedia.org/wiki/HP_Software_Division? HP Software Division]
|-
| [http://en.wikipedia.org/wiki/Software_release_life_cycle? Stable release] || 12.01
|-
| [http://en.wikipedia.org/wiki/Operating_system? Operating system] || [http://en.wikipedia.org/wiki/Microsoft_Windows? Microsoft Windows]
|-
| [http://en.wikipedia.org/wiki/List_of_software_categories? Type] || [http://en.wikipedia.org/wiki/Test_automation? Test automation tools]
|-
| [http://en.wikipedia.org/wiki/Software_license? License] || [http://en.wikipedia.org/wiki/Proprietary_software? Proprietary]
|}

=='''Background'''==
Test automation is the use of software to control the execution of tests cases, the comparison of actual to predicted results, the setting up of test preconditions, and other test control and test reporting functions.<ref>''The Testing Network, An Integral Approach to Test Activities in Large Software Projects'' by Jean-Jacques Pierre Henry (Aug 17, 2008), p413, ISBN 978-3-540-78504-0</ref> Test Automation is a development discipline as it uses scripting languages to instruct the tool how to interact with your application. As such careful consideration needs to be paid to

* Exception handling for bugs that occur during testing cycles(i.e, unexpected error messages during a test run).
* How the tool synchronizes with your application(e.g. if there are slow response times from your environment)
* The level of maintenance required to keep the tests up to date with changes in the application [http://en.wikipedia.org/wiki/Graphical_user_interface GUI](i.e, new buttons, data fields, custom controls etc)

Any test automation framework is a set of assumptions, concepts and tools that provide support for automating the major activities in the testing process. The main advantage of a framework is

* Increased Productivity
* Easy and Reduced maintenance effort
* Consistent automation development across projects
* Process driven than person driven approach
* Controlled maintenance of automation artifacts

There is a range of automation testing tools available. Some of them are licensed and few others are open sourced. QTP, Cucumber, Capybara and other tools<ref>http://en.wikipedia.org/wiki/List_of_web_testing_tools</ref>

=='''Description'''==
Although HP UFT is generally used for GUI based Test Case Automation, it can also automate some non-GUI based test cases like database testing, webservice testing and file based operations. It offers a graphical user interface, keyboard support, multiple testing views, and scripting language.
<ref>http://www.softwaretestinghelp.com/qtp-quicktest-professional-tutorial-1/</ref>
===Data Driven Testing===
HP Unified Functional Testing allows us to perform data-driven testing. For example, data can be output to a data table for reuse. [http://en.wikipedia.org/wiki/Data-driven_testing Data-driven testing] is implemented as a Microsoft Excel workbook, which is accessible from HP Unified Functional Testing. HP Unified Functional Testing has two data tables: the Global data sheet and Action (local) data sheets. The test steps can read data from these data tables in order to drive variable data into the application under test, and verify the expected result.<ref>http://www.qtp10.com/2009/07/using-global-and-action-data-sheets-in.html</ref>

===Views===
HP Unified Functional Testing provides two views—and ways to modify—a test script: Keyword View and Expert View. These views enable HP Unified Functional Testing to act as an Integrated Development Environment (IDE) for the test, and HP Unified Functional Testing includes many standard IDE features, such as breakpoints to pause a test at predetermined places.<ref>http://en.wikipedia.org/wiki/HP_QuickTest_Professional</ref>

====Keyword view====
Keyword View lets users create and view the steps of a test in a modular, table format. In Keyword View, users can also view properties for items such as checkpoints, output values, and actions, use conditional and loop statements, and insert breakpoints to assist in debugging a test.<ref>http://www.qtp10.com/2009/07/working-with-keyword-view-in-hp-qtp.html</ref>

====Expert View====
Expert view displays test code using [http://en.wikipedia.org/wiki/VBScript VBScript]. Designed for more advanced users, users can edit all test actions except for the root Global action, and changes are synchronized with the Keyword View.<ref>http://www.fdscallcentre.com/homepage/data/mi/DS-0413-020_QTPro6.0.pdf</ref>

===Scripting===
HP UFT's VBScript allows for classes, but not other object oriented properties such as inheritance and polymorphism. It also lacks a debugger, however UFT has a debugger provided by HP. Some Windows script ([http://en.wikipedia.org/wiki/Windows_Script_Host WScript],[http://en.wikipedia.org/wiki/WSH WSH],[http://en.wikipedia.org/wiki/Wmii WMI]) & [http://en.wikipedia.org/wiki/Visual_Basic_.NET VB.Net] code can be used in a script in the expert view <ref>https://h20546.www2.hp.com/main/training/course_details.cfm?Course=00008165&sitepick=US</ref>

===Example===
QTP script for opening a Notepad file<ref>http://kuldeepse.wordpress.com/2007/11/11/qtp-script-for-sending-a-mail-using-outlook/</ref>.
<pre>invokeapplication”c:/whatever the path”
Run
Dim a
Set a = WScript.CreateObject (“WSCript.shell”)
a.run “notepad.exe”

Dim oShell
Set oShell = CreateObject (“WSCript.shell”)
oShell.run “cmd/notepad.exe”
Set oShell = Nothing

DsystemUtil.Run “Notepad.exe”
</pre>
===Exception handling===
Application crashes, Unexpected events and errors during a run session can interrupt the run session and mislead results. This is a problem particularly when tests run unattended—the test pauses until one performs the operation needed to recover. To handle these situations, Exception Handling and Error handling is must while developing script or Automation Framework.<ref>http://qtpautomationcodes.blogspot.com/2013/05/error-handling-in-qtp.html</ref>
Error and Exception handling in HP UFT can be done by any of the following ways:

* [http://www.softwaretestinghelp.com/conditional-loop-statements-qtp-tutorial-4/ Conditional Statement]
* [http://www.tutorialspoint.com/qtp/qtp_error_handling.htm On Error statement]
* [http://www.tutorialspoint.com/qtp/qtp_recovery_scenarios.htm Recovery Scenarios]

=='''Life Cycle'''==
A typical [http://www.learnqtp.com/forums/Thread-Automation-Life-Cycle life cycle] of HP UFT looks like this.

[[File:LifeCycle.jpg‎]]

=='''Comparison to other tools'''==
Tools like [http://en.wikipedia.org/wiki/Cucumber_(software) Cucumber] and [http://rubygems.org/gems/capybara Capybara] run tests from the viewpoint of the user. Cucumber translates user stories into tests and Capybara simulates a user or web browser. Unified Functional Testing is used by programmers to preform specific test cases they code themselves.<ref>''Engineering Long-Lasting Software: An Agile Approach Using SaaS and Cloud Computing'', Beta Edition 0.9.0 by Armando Fox and David Patterson, August 23, 2012, p136, </ref>

'''Capybara''' talks to a website, just like a human would do (example: visit a url, click on the specific area of the sceen, input data and submit the form). It imitates user flow over website. Test cases in Capybara will look like this:<ref>http://stackoverflow.com/questions/15004918/cucumber-vs-capybara</ref>
<pre>
describe "the signup process", :type => :feature do
before :each do
User.make(:email => 'user@example.com', :password => 'caplin')
end
it "signs me in" do
visit '/sessions/new'
within("#session") do
fill_in 'Login', :with => 'user@example.com'
fill_in 'Password', :with => 'password'
end
click_link 'Sign in'
page.should have_content 'Success'
end
end</pre>

'''Cucumber''' tests are very much human readable. Example:<ref>http://stackoverflow.com/questions/15004918/cucumber-vs-capybara</ref>

<pre>
Scenario: Signup process
Given a user exists with email "user@example.com" and password "caplin"
When I try to login with "user@example.com" and "caplin"
Then I should be logged in successfully
</pre>

[http://en.wikipedia.org/wiki/Selenium Selenium] is a tool for automating web applications for testing purposes.

'''Comparison of UFT with other tools'''<ref>http://www.aspiresys.com/WhitePapers/QTPvsSelenium.pdf</ref>
{| border="1" class="wikitable"
|+
! Feature
! UFT
! Selenium
! Cucumber/ Capybara
|-
! Windows (Non-browser)
based Application support
| Yes
| No
| No
|-
! Environment Support
| Only Windows
| Windows , Linux , Solaris
OS X , Others
| Windows , Linux , Solaris
OS X , Others
|-
! Windows (Non-browser)
based Application support
| Yes
| No
| No
|-
!Software Cost
| License & Annual maintenance Fees
| Zero
| Zero
|-
!Coding Experience of
Engineer
|Not Much
|Should be very good along with
technical capabilities of integrating
different pieces of framework
|Requires minimal use of Ruby programming
|-
!Script written in
|VBScript
|Java, Ruby, Python, C#, and PHP
|Ruby
|-
!Script Creation Time
|Low
|High
|Medium
|-
!Hardware resource (CPU
+ RAM) consumption during
script execution
|High
|Low
|Low
|-
!Product Support
|Dedicate HP support along with
support forums
|Open Source Community
|Open Source Community
|-
!Framework
|Easily integrated with [http://en.wikipedia.org/wiki/HP_Quality_Center HP Quality Center] or [http://en.wikipedia.org/wiki/HP_Application_Lifecycle_Management HP ALM]
|Selenium + Eclipse + [http://en.wikipedia.org/wiki/MAVEN Maven] / [http://en.wikipedia.org/wiki/Apache_Ant ANT]
+[http://en.wikipedia.org/wiki/Jenkins_(software) Jenkins] / [http://en.wikipedia.org/wiki/Hudson_(software) Hudson] & its plugins /
Cruise Control + [http://en.wikipedia.org/wiki/TestNG TestNG] + [http://en.wikipedia.org/wiki/Apache_Subversion SVN]
|Ruby on Rails
[http://en.wikipedia.org/wiki/Merb Merb]

[http://en.wikipedia.org/wiki/Sinatra_(software) Sinatra]
|-
!Continuous Integration
|Possible through Quality Center
/ ALM or Jenkins
|Possible through Jenkins / Hudson
/ Cruise Control
|Possible through Rake, Ant, Maven and [http://en.wikipedia.org/wiki/JUnit JUnit] output
|}

=='''Disadvantages'''==
UFT popularity is slowly shrinking.<ref>http://www.quora.com/Is-there-demand-for-QTP</ref> It is being used more for legacy applications.

People are moving away from UFT because of it's reactive approach of writing test automation. Testers write the scripts. With cucumber, capybara and selenium, automation test are joint effort between developers and the testers. The testers write the test cases in cucumber scenario format, then the developers write the steps definition. This way, everyone is contributing and everyone is reviewing the test cases. Cucumber code is readable and easy to understand.<ref>http://qastuffs.blogspot.com/2010_12_01_archive.html</ref>

=='''References'''==
<references/>

CSC/ECE 517 Fall 2014/ch1a 22 as

2014-09-25T08:56:48Z

Abora:

'''HP Unified Functional Testing Professional'''

'''HP Unified Functional Testing (UFT)''' software, previously known as '''HP Quick Test Professional (QTP)''',<ref>http://www.automationrepository.com/2012/12/hp-unified-functional-testing-uft-11-5-new-features</ref> provides [http://en.wikipedia.org/wiki/Functional_testing functional testing] and [http://en.wikipedia.org/wiki/Regression_testing regression testing] automation for software applications.<ref>http://www8.hp.com/us/en/software-solutions/application-lifecycle-management-application-test-software/index.html?zn=bto&cp=1-11-127-24^1352_4000_1__</ref> HP Unified Functional Testing can be used for enterprise [http://en.wikipedia.org/wiki/Quality_assurance quality assurance].<ref>http://www.learnqtp.com/qtp-quality-center-test-director-guide/</ref> HP Unified Functional Testing is a test automation tool originally developed by [http://en.wikipedia.org/wiki/Mercury_Interactive Mercury Interactive] and later acquired by [http://en.wikipedia.org/wiki/Hewlett-Packard Hewlett Packard].<ref> http://www.devbistro.com/articles/Testing/Mercury-QuickTest-Professional-Evaluation</ref> HP Unified Functional Testing 11.5 combined HP QuickTest Professional and HP Service Test into a single software package,<ref> http://selftechy.com/2013/10/07/hp-uft-11-50-unified-functional-testing</ref> which is currently available from the HP Software Division. The integrated HP Unified Functional Testing software allows developers to test from a single console all three layers of a program’s operations: the interface, [http://en.wikipedia.org/wiki/Service_layer the service layer] and the database layer.<ref>http://www.computerworld.com/article/2493313/data-center/hp-simplifies-automated-software-testing-suite.html</ref>

[https://docs.google.com/document/d/1eq3XHiUUBIrEBx-R2Mgolaw7HttSgzPniwDLEF5oVk0/edit# Writeup page.]
{| align=right style="border: 1px solid gray;" class="wikitable"
|+ HP Uniffied Functional Testing<ref>http://en.wikipedia.org/wiki/HP_QuickTest_Professional</ref>
|-
| [http://en.wikipedia.org/wiki/Software_developer? Developer(s)] || [http://en.wikipedia.org/wiki/Hewlett-Packard? HP], [http://en.wikipedia.org/wiki/HP_Software_Division? HP Software Division]
|-
| [http://en.wikipedia.org/wiki/Software_release_life_cycle? Stable release] || 12.01
|-
| [http://en.wikipedia.org/wiki/Operating_system? Operating system] || [http://en.wikipedia.org/wiki/Microsoft_Windows? Microsoft Windows]
|-
| [http://en.wikipedia.org/wiki/List_of_software_categories? Type] || [http://en.wikipedia.org/wiki/Test_automation? Test automation tools]
|-
| [http://en.wikipedia.org/wiki/Software_license? License] || [http://en.wikipedia.org/wiki/Proprietary_software? Proprietary]
|}

=='''Background'''==
Test automation is the use of software to control the execution of tests cases, the comparison of actual to predicted results, the setting up of test preconditions, and other test control and test reporting functions.<ref>''The Testing Network, An Integral Approach to Test Activities in Large Software Projects'' by Jean-Jacques Pierre Henry (Aug 17, 2008), p413, ISBN 978-3-540-78504-0</ref> Test Automation is a development discipline as it uses scripting languages to instruct the tool how to interact with your application. As such careful consideration needs to be paid to

* Exception handling for bugs that occur during testing cycles(i.e, unexpected error messages during a test run).
* How the tool synchronizes with your application(e.g. if there are slow response times from your environment)
* The level of maintenance required to keep the tests up to date with changes in the application [http://en.wikipedia.org/wiki/Graphical_user_interface GUI](i.e, new buttons, data fields, custom controls etc)

Any test automation framework is a set of assumptions, concepts and tools that provide support for automating the major activities in the testing process. The main advantage of a framework is

* Increased Productivity
* Easy and Reduced maintenance effort
* Consistent automation development across projects
* Process driven than person driven approach
* Controlled maintenance of automation artifacts

There is a range of automation testing tools available. Some of them are licensed and few others are open sourced. QTP, Cucumber, Capybara and other tools<ref>http://en.wikipedia.org/wiki/List_of_web_testing_tools</ref>

=='''Description'''==
Although HP UFT is generally used for GUI based Test Case Automation, it can also automate some non-GUI based test cases like database testing, webservice testing and file based operations. It offers a graphical user interface, keyboard support, multiple testing views, and scripting language.
<ref>http://www.softwaretestinghelp.com/qtp-quicktest-professional-tutorial-1/</ref>
===Data Driven Testing===
HP Unified Functional Testing allows us to perform data-driven testing. For example, data can be output to a data table for reuse. [http://en.wikipedia.org/wiki/Data-driven_testing Data-driven testing] is implemented as a Microsoft Excel workbook, which is accessible from HP Unified Functional Testing. HP Unified Functional Testing has two data tables: the Global data sheet and Action (local) data sheets. The test steps can read data from these data tables in order to drive variable data into the application under test, and verify the expected result.<ref>http://www.qtp10.com/2009/07/using-global-and-action-data-sheets-in.html</ref>

===Views===
HP Unified Functional Testing provides two views—and ways to modify—a test script: Keyword View and Expert View. These views enable HP Unified Functional Testing to act as an Integrated Development Environment (IDE) for the test, and HP Unified Functional Testing includes many standard IDE features, such as breakpoints to pause a test at predetermined places.<ref>http://en.wikipedia.org/wiki/HP_QuickTest_Professional</ref>

====Keyword view====
Keyword View lets users create and view the steps of a test in a modular, table format. In Keyword View, users can also view properties for items such as checkpoints, output values, and actions, use conditional and loop statements, and insert breakpoints to assist in debugging a test.<ref>http://www.qtp10.com/2009/07/working-with-keyword-view-in-hp-qtp.html</ref>

====Expert View====
Expert view displays test code using [http://en.wikipedia.org/wiki/VBScript VBScript]. Designed for more advanced users, users can edit all test actions except for the root Global action, and changes are synchronized with the Keyword View.<ref>http://www.fdscallcentre.com/homepage/data/mi/DS-0413-020_QTPro6.0.pdf</ref>

===Scripting===
HP UFT's VBScript allows for classes, but not other object oriented properties such as inheritance and polymorphism. It also lacks a debugger, however UFT has a debugger provided by HP. Some Windows script ([http://en.wikipedia.org/wiki/Windows_Script_Host WScript],[http://en.wikipedia.org/wiki/WSH WSH],[http://en.wikipedia.org/wiki/Wmii WMI]) & [http://en.wikipedia.org/wiki/Visual_Basic_.NET VB.Net] code can be used in a script in the expert view <ref>https://h20546.www2.hp.com/main/training/course_details.cfm?Course=00008165&sitepick=US</ref>

===Example===
QTP script for opening a Notepad file<ref>http://kuldeepse.wordpress.com/2007/11/11/qtp-script-for-sending-a-mail-using-outlook/</ref>.
<pre>invokeapplication”c:/whatever the path”
Run
Dim a
Set a = WScript.CreateObject (“WSCript.shell”)
a.run “notepad.exe”

Dim oShell
Set oShell = CreateObject (“WSCript.shell”)
oShell.run “cmd/notepad.exe”
Set oShell = Nothing

DsystemUtil.Run “Notepad.exe”
</pre>
===Exception handling===
Application crashes, Unexpected events and errors during a run session can interrupt the run session and mislead results. This is a problem particularly when tests run unattended—the test pauses until one performs the operation needed to recover. To handle these situations, Exception Handling and Error handling is must while developing script or Automation Framework.<ref>http://qtpautomationcodes.blogspot.com/2013/05/error-handling-in-qtp.html</ref>
Error and Exception handling in HP UFT can be done by any of the following ways:

* [http://www.softwaretestinghelp.com/conditional-loop-statements-qtp-tutorial-4/ Conditional Statement]
* [http://www.tutorialspoint.com/qtp/qtp_error_handling.htm On Error statement]
* [http://www.tutorialspoint.com/qtp/qtp_recovery_scenarios.htm Recovery Scenarios]

=='''Life Cycle'''==
A typical [http://www.learnqtp.com/forums/Thread-Automation-Life-Cycle life cycle] of HP UFT looks like this.

[[File:LifeCycle.jpg‎]]

=='''Comparison to other tools'''==
Tools like [http://en.wikipedia.org/wiki/Cucumber_(software) Cucumber] and [http://rubygems.org/gems/capybara Capybara] run tests from the viewpoint of the user. Cucumber translates user stories into tests and Capybara simulates a user or web browser. Unified Functional Testing is used by programmers to preform specific test cases they code themselves.<ref>''Engineering Long-Lasting Software: An Agile Approach Using SaaS and Cloud Computing'', Beta Edition 0.9.0 by Armando Fox and David Patterson, August 23, 2012, p136, </ref>

'''Capybara''' talks to a website, just like a human would do (example: visit a url, click on the specific area of the sceen, input data and submit the form). It imitates user flow over website. Test cases in Capybara will look like this:<ref>http://stackoverflow.com/questions/15004918/cucumber-vs-capybara</ref>
<pre>
describe "the signup process", :type => :feature do
before :each do
User.make(:email => 'user@example.com', :password => 'caplin')
end
it "signs me in" do
visit '/sessions/new'
within("#session") do
fill_in 'Login', :with => 'user@example.com'
fill_in 'Password', :with => 'password'
end
click_link 'Sign in'
page.should have_content 'Success'
end
end</pre>

'''Cucumber''' tests are very much human readable. Example:<ref>http://stackoverflow.com/questions/15004918/cucumber-vs-capybara</ref>

<pre>
Scenario: Signup process
Given a user exists with email "user@example.com" and password "caplin"
When I try to login with "user@example.com" and "caplin"
Then I should be logged in successfully
</pre>

[http://en.wikipedia.org/wiki/Selenium Selenium] is a tool for automating web applications for testing purposes.

'''Comparison of UFT with other tools'''<ref>http://www.aspiresys.com/WhitePapers/QTPvsSelenium.pdf</ref>
{| border="1" class="wikitable"
|+
! Feature
! UFT
! Selenium
! Cucumber/ Capybara
|-
! Windows (Non-browser)
based Application support
| Yes
| No
| No
|-
! Environment Support
| Only Windows
| Windows , Linux , Solaris
OS X , Others
| Windows , Linux , Solaris
OS X , Others
|-
! Windows (Non-browser)
based Application support
| Yes
| No
| No
|-
!Software Cost
| License & Annual maintenance Fees
| Zero
| Zero
|-
!Coding Experience of
Engineer
|Not Much
|Should be very good along with
technical capabilities of integrating
different pieces of framework
|Requires minimal use of Ruby programming
|-
!Script Creation Time
|Low
|High
|Medium
|-
!Hardware resource (CPU
+ RAM) consumption during
script execution
|High
|Low
|Low
|-
!Product Support
|Dedicate HP support along with
support forums
|Open Source Community
|Open Source Community
|-
!Framework
|Easily integrated with [http://en.wikipedia.org/wiki/HP_Quality_Center HP Quality Center] or [http://en.wikipedia.org/wiki/HP_Application_Lifecycle_Management HP ALM]
|Selenium + Eclipse + [http://en.wikipedia.org/wiki/MAVEN Maven] / [http://en.wikipedia.org/wiki/Apache_Ant ANT]
+[http://en.wikipedia.org/wiki/Jenkins_(software) Jenkins] / [http://en.wikipedia.org/wiki/Hudson_(software) Hudson] & its plugins /
Cruise Control + [http://en.wikipedia.org/wiki/TestNG TestNG] + [http://en.wikipedia.org/wiki/Apache_Subversion SVN]
|Ruby on Rails
[http://en.wikipedia.org/wiki/Merb Merb]

[http://en.wikipedia.org/wiki/Sinatra_(software) Sinatra]
|-
!Continuous Integration
|Possible through Quality Center
/ ALM or Jenkins
|Possible through Jenkins / Hudson
/ Cruise Control
|Possible through Rake, Ant, Maven and [http://en.wikipedia.org/wiki/JUnit JUnit] output
|}

=='''Disadvantages'''==
UFT popularity is slowly shrinking.<ref>http://www.quora.com/Is-there-demand-for-QTP</ref> It is being used more for legacy applications.

People are moving away from UFT because of it's reactive approach of writing test automation. Testers write the scripts. With cucumber, capybara and selenium, automation test are joint effort between developers and the testers. The testers write the test cases in cucumber scenario format, then the developers write the steps definition. This way, everyone is contributing and everyone is reviewing the test cases. Cucumber code is readable and easy to understand.<ref>http://qastuffs.blogspot.com/2010_12_01_archive.html</ref>

Unified Functional Testing is developed mainly for Windows based systems and it relies on outdated Windows tools like VBXScript. Tests can not be run outside of the UFT environment nor are they compatible with all browser types.<ref>http://www8.hp.com/us/en/software-solutions/unified-functional-testing-automated-testing/demos-documents.html#!&pd1=1</ref>

=='''References'''==
<references/>

CSC/ECE 517 Fall 2014/ch1a 22 as

2014-09-16T17:59:15Z

Abora:

'''HP Unified Functional Testing Professional'''

HP Unified Functional Testing (UFT) software, formerly known as HP Quick Test Professional (QTP),<ref>http://www.automationrepository.com/2012/12/hp-unified-functional-testing-uft-11-5-new-features</ref> provides [http://en.wikipedia.org/wiki/Functional_testing functional testing] and [http://en.wikipedia.org/wiki/Regression_testing regression testing] automation for software applications and environments.<ref>http://www8.hp.com/us/en/software-solutions/application-lifecycle-management-application-test-software/index.html?zn=bto&cp=1-11-127-24^1352_4000_1__</ref> HP Unified Functional Testing can be used for enterprise [http://en.wikipedia.org/wiki/Quality_assurance quality assurance].<ref>http://www.learnqtp.com/qtp-quality-center-test-director-guide/</ref> HP Unified Functional Testing is a test automation tool originally developed by [http://en.wikipedia.org/wiki/Mercury_Interactive Mercury Interactive] and later acquired by [http://en.wikipedia.org/wiki/Hewlett-Packard Hewlett Packard].<ref> http://www.devbistro.com/articles/Testing/Mercury-QuickTest-Professional-Evaluation</ref> HP Unified Functional Testing 11.5 combined HP QuickTest Professional and HP Service Test into a single software package,<ref> http://selftechy.com/2013/10/07/hp-uft-11-50-unified-functional-testing</ref> which is currently available from the HP Software Division. The integrated HP Unified Functional Testing software allows developers to test from a single console all three layers of a program’s operations: the interface, [http://en.wikipedia.org/wiki/Service_layer the service layer] and the database layer.<ref>http://www.computerworld.com/article/2493313/data-center/hp-simplifies-automated-software-testing-suite.html</ref>

[https://docs.google.com/document/d/1eq3XHiUUBIrEBx-R2Mgolaw7HttSgzPniwDLEF5oVk0/edit# Writeup page.]
{| align=right style="border: 1px solid gray;" class="wikitable"
|+ HP Uniffied Functional Testing<ref>http://en.wikipedia.org/wiki/HP_QuickTest_Professional</ref>
|-
| [http://en.wikipedia.org/wiki/Software_developer? Developer(s)] || [http://en.wikipedia.org/wiki/Hewlett-Packard? HP], [http://en.wikipedia.org/wiki/HP_Software_Division? HP Software Division]
|-
| [http://en.wikipedia.org/wiki/Software_release_life_cycle? Stable release] || 12.01
|-
| [http://en.wikipedia.org/wiki/Operating_system? Operating system] || [http://en.wikipedia.org/wiki/Microsoft_Windows? Microsoft Windows]
|-
| [http://en.wikipedia.org/wiki/List_of_software_categories? Type] || [http://en.wikipedia.org/wiki/Test_automation? Test automation tools]
|-
| [http://en.wikipedia.org/wiki/Software_license? License] || [http://en.wikipedia.org/wiki/Proprietary_software? Proprietary]
|}

=='''Background'''==
Test automation is the use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions.<ref>''The Testing Network, An Integral Approach to Test Activities in Large Software Projects'' by Jean-Jacques Pierre Henry (Aug 17, 2008), p413, ISBN 978-3-540-78504-0</ref> Test Automation is a development discipline as it uses scripting languages to instruct the tool how to interact with your application. As such careful consideration needs to be paid to

* Exception handling for bugs that occur during testing cycles(i.e, unexpected error messages during a test run).
* How the tool synchronizes with your application(e.g. if there are slow response times from your environment)
* The level of maintenance required to keep the tests up to date with changes in the application [http://en.wikipedia.org/wiki/Graphical_user_interface GUI](i.e, new buttons, data fields, custom controls etc)

Any test automation framework is a set of assumptions, concepts and tools that provide support for automating the major activities in the testing process. The main advantage of a framework is

* Increased Productivity
* Easy and Reduced maintenance effort
* Consistent automation development across projects
* Process driven than person driven approach
* Controlled maintenance of automation artifacts

There is a range of automation testing tools available. Some of them are licensed and few others are open sourced. QTP, Cucumber, Capybara and other tools<ref>http://en.wikipedia.org/wiki/List_of_web_testing_tools</ref>

=='''Description'''==
Although HP UFT is usually used for UI based Test Case Automation, it can also automate some non-UI based test cases like database testing, webservice testing and file based operations. It offers a graphical user interface, keyboard support, multiple testing views, and scripting language.
<ref>http://www.softwaretestinghelp.com/qtp-quicktest-professional-tutorial-1/</ref>
===Data Driven Testing===
HP Unified Functional Testing supports data-driven testing. For example, data can be output to a data table for reuse elsewhere. [http://en.wikipedia.org/wiki/Data-driven_testing Data-driven testing] is implemented as a Microsoft Excel workbook that can be accessed from HP Unified Functional Testing. HP Unified Functional Testing has two types of data tables: the Global data sheet and Action (local) data sheets. The test steps can read data from these data tables in order to drive variable data into the application under test, and verify the expected result.<ref>http://www.qtp10.com/2009/07/using-global-and-action-data-sheets-in.html</ref>

===Views===
HP Unified Functional Testing provides two views—and ways to modify—a test script: Keyword View and Expert View. These views enable HP Unified Functional Testing to act as an Integrated Development Environment (IDE) for the test, and HP Unified Functional Testing includes many standard IDE features, such as breakpoints to pause a test at predetermined places.<ref>http://en.wikipedia.org/wiki/HP_QuickTest_Professional</ref>

====Keyword view====
Keyword View lets users create and view the steps of a test in a modular, table format. In Keyword View, users can also view properties for items such as checkpoints, output values, and actions, use conditional and loop statements, and insert breakpoints to assist in debugging a test.<ref>http://www.qtp10.com/2009/07/working-with-keyword-view-in-hp-qtp.html</ref>

====Expert View====
Expert view displays test code using [http://en.wikipedia.org/wiki/VBScript VBScript]. Designed for more advanced users, users can edit all test actions except for the root Global action, and changes are synchronized with the Keyword View.<ref>http://www.fdscallcentre.com/homepage/data/mi/DS-0413-020_QTPro6.0.pdf</ref>

===Scripting===
HP UFT's VBScript allows for classes, but not other object oriented properties such as inheritance and polymorphism. It also lacks a debugger, however UFT has a debugger provided by HP. Some Windows script ([http://en.wikipedia.org/wiki/Windows_Script_Host WScript],[http://en.wikipedia.org/wiki/WSH WSH],[http://en.wikipedia.org/wiki/Wmii WMI]) & [http://en.wikipedia.org/wiki/Visual_Basic_.NET VB.Net] code can be used in a script in the expert view <ref>https://h20546.www2.hp.com/main/training/course_details.cfm?Course=00008165&sitepick=US</ref>

===Exception handling===
Application crashes, Unexpected events and errors during a run session can disrupt the run session and distort results. This is a problem particularly when tests run unattended—the test pauses until one performs the operation needed to recover. To handle such situations, Error and Exception Handling is must while developing script or Automation Framework.<ref>http://qtpautomationcodes.blogspot.com/2013/05/error-handling-in-qtp.html</ref>
Error and Exception handling in HP UFT can be done by the following ways:

* [http://www.softwaretestinghelp.com/conditional-loop-statements-qtp-tutorial-4/ Conditional Statement]
* [http://www.tutorialspoint.com/qtp/qtp_error_handling.htm On Error statement]
* [http://www.tutorialspoint.com/qtp/qtp_recovery_scenarios.htm Recovery Scenarios]

=='''Life Cycle'''==
A typical [http://www.learnqtp.com/forums/Thread-Automation-Life-Cycle life cycle] of HP UFT looks like this.

[[File:LifeCycle.jpg‎]]

=='''Comparison to other tools'''==
Tools like [http://en.wikipedia.org/wiki/Cucumber_(software) Cucumber] and [http://rubygems.org/gems/capybara Capybara] run tests from the viewpoint of the user. Cucumber translates user stories into tests and Capybara simulates a user or web browser. Unified Functional Testing is used by programmers to preform specific test cases they code themselves.<ref>''Engineering Long-Lasting Software: An Agile Approach Using SaaS and Cloud Computing'', Beta Edition 0.9.0 by Armando Fox and David Patterson, August 23, 2012, p136, </ref>

'''Capybara''' talks to a website, just like a human would do (example: visit a url, click on the specific area of the sceen, input data and submit the form). It imitates user flow over website. Test cases in Capybara will look like this:<ref>http://stackoverflow.com/questions/15004918/cucumber-vs-capybara</ref>
<pre>
describe "the signup process", :type => :feature do
before :each do
User.make(:email => 'user@example.com', :password => 'caplin')
end
it "signs me in" do
visit '/sessions/new'
within("#session") do
fill_in 'Login', :with => 'user@example.com'
fill_in 'Password', :with => 'password'
end
click_link 'Sign in'
page.should have_content 'Success'
end
end</pre>

'''Cucumber''' tests are very much human readable. Example:<ref>http://stackoverflow.com/questions/15004918/cucumber-vs-capybara</ref>

<pre>
Scenario: Signup process
Given a user exists with email "user@example.com" and password "caplin"
When I try to login with "user@example.com" and "caplin"
Then I should be logged in successfully
</pre>

[http://en.wikipedia.org/wiki/Selenium Selenium] is a tool for automating web applications for testing purposes.

'''Comparison of UFT with other tools'''<ref>http://www.aspiresys.com/WhitePapers/QTPvsSelenium.pdf</ref>
{| border="1" class="wikitable"
|+
! Feature
! UFT
! Selenium
! Cucumber/ Capybara
|-
! Windows (Non-browser)
based Application support
| Yes
| No
| No
|-
! Environment Support
| Only Windows
| Windows , Linux , Solaris
OS X , Others
| Windows , Linux , Solaris
OS X , Others
|-
! Windows (Non-browser)
based Application support
| Yes
| No
| No
|-
!Software Cost
| License & Annual maintenance Fees
| Zero
| Zero
|-
!Coding Experience of
Engineer
|Not Much
|Should be very good along with
technical capabilities of integrating
different pieces of framework
|Requires minimal use of Ruby programming
|-
!Script Creation Time
|Low
|High
|Medium
|-
!Hardware resource (CPU
+ RAM) consumption during
script execution
|High
|Low
|Low
|-
!Product Support
|Dedicate HP support along with
support forums
|Open Source Community
|Open Source Community
|-
!Framework
|Easily integrated with [http://en.wikipedia.org/wiki/HP_Quality_Center HP Quality Center] or [http://en.wikipedia.org/wiki/HP_Application_Lifecycle_Management HP ALM]
|Selenium + Eclipse + [http://en.wikipedia.org/wiki/MAVEN Maven] / [http://en.wikipedia.org/wiki/Apache_Ant ANT]
+[http://en.wikipedia.org/wiki/Jenkins_(software) Jenkins] / [http://en.wikipedia.org/wiki/Hudson_(software) Hudson] & its plugins /
Cruise Control + [http://en.wikipedia.org/wiki/TestNG TestNG] + [http://en.wikipedia.org/wiki/Apache_Subversion SVN]
|Ruby on Rails
[http://en.wikipedia.org/wiki/Merb Merb]

[http://en.wikipedia.org/wiki/Sinatra_(software) Sinatra]
|-
!Continuous Integration
|Possible through Quality Center
/ ALM or Jenkins
|Possible through Jenkins / Hudson
/ Cruise Control
|Possible through Rake, Ant, Maven and JUnit output
|}

=='''Disadvantages'''==
UFT popularity is slowly shrinking.<ref>http://www.quora.com/Is-there-demand-for-QTP</ref> It is being used more in legacy application.

People are moving away from UFT because of it's reactive approach of writing test automation. Testers write the scripts. With cucumber, capybara and selenium, automation test are joint effort between developers and the testers. The testers write the test cases in cucumber scenario format, then the developers write the steps definition. This way, everyone is contributing and everyone is reviewing the test cases. Cucumber code is readable and easy to understand.<ref>http://qastuffs.blogspot.com/2010_12_01_archive.html</ref>

Unified Functional Testing is developed mainly for Windows based systems and it relies on outdated Windows tools like VBXScript. Tests can not be run outside of the UFT environment nor are they compatible with all browser types.<ref>http://www8.hp.com/us/en/software-solutions/unified-functional-testing-automated-testing/demos-documents.html#!&pd1=1</ref>

=='''References'''==
<references/>

CSC/ECE 517 Fall 2014/ch1a 22 as

2014-09-16T01:58:14Z

Abora:

'''HP Unified Functional Testing Professional'''

HP Unified Functional Testing (UFT) software, formerly known as HP Quick Test Professional (QTP),<ref>http://www.automationrepository.com/2012/12/hp-unified-functional-testing-uft-11-5-new-features</ref> provides [http://en.wikipedia.org/wiki/Functional_testing functional testing] and [http://en.wikipedia.org/wiki/Regression_testing regression testing] automation for software applications and environments.<ref>http://www8.hp.com/us/en/software-solutions/application-lifecycle-management-application-test-software/index.html?zn=bto&cp=1-11-127-24^1352_4000_1__</ref> HP Unified Functional Testing can be used for enterprise [http://en.wikipedia.org/wiki/Quality_assurance quality assurance].<ref>http://www.learnqtp.com/qtp-quality-center-test-director-guide/</ref> HP Unified Functional Testing is a test automation tool originally developed by [http://en.wikipedia.org/wiki/Mercury_Interactive Mercury Interactive] and later acquired by [http://en.wikipedia.org/wiki/Hewlett-Packard Hewlett Packard].<ref> http://www.devbistro.com/articles/Testing/Mercury-QuickTest-Professional-Evaluation</ref> HP Unified Functional Testing 11.5 combined HP QuickTest Professional and HP Service Test into a single software package,<ref> http://selftechy.com/2013/10/07/hp-uft-11-50-unified-functional-testing</ref> which is currently available from the HP Software Division. The integrated HP Unified Functional Testing software allows developers to test from a single console all three layers of a program’s operations: the interface, [http://en.wikipedia.org/wiki/Service_layer the service layer] and the database layer.<ref>http://www.computerworld.com/article/2493313/data-center/hp-simplifies-automated-software-testing-suite.html</ref>

[https://docs.google.com/document/d/1eq3XHiUUBIrEBx-R2Mgolaw7HttSgzPniwDLEF5oVk0/edit# Writeup page.]
{| align=right style="border: 1px solid gray;" class="wikitable"
|+ HP Uniffied Functional Testing<ref>http://en.wikipedia.org/wiki/HP_QuickTest_Professional</ref>
|-
| [http://en.wikipedia.org/wiki/Software_developer? Developer(s)] || [http://en.wikipedia.org/wiki/Hewlett-Packard? HP], [http://en.wikipedia.org/wiki/HP_Software_Division? HP Software Division]
|-
| [http://en.wikipedia.org/wiki/Software_release_life_cycle? Stable release] || 12.01
|-
| [http://en.wikipedia.org/wiki/Operating_system? Operating system] || [http://en.wikipedia.org/wiki/Microsoft_Windows? Microsoft Windows]
|-
| [http://en.wikipedia.org/wiki/List_of_software_categories? Type] || [http://en.wikipedia.org/wiki/Test_automation? Test automation tools]
|-
| [http://en.wikipedia.org/wiki/Software_license? License] || [http://en.wikipedia.org/wiki/Proprietary_software? Proprietary]
|}

=='''Background'''==
Test automation is the use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions.<ref>''The Testing Network, An Integral Approach to Test Activities in Large Software Projects'' by Jean-Jacques Pierre Henry (Aug 17, 2008), p413, ISBN 978-3-540-78504-0</ref> Test Automation is a development discipline as it uses scripting languages to instruct the tool how to interact with your application. As such careful consideration needs to be paid to

* Exception handling for bugs that occur during testing cycles(i.e, unexpected error messages during a test run).
* How the tool synchronizes with your application(e.g. if there are slow response times from your environment)
* The level of maintenance required to keep the tests up to date with changes in the application [http://en.wikipedia.org/wiki/Graphical_user_interface GUI](i.e, new buttons, data fields, custom controls etc)

Any test automation framework is a set of assumptions, concepts and tools that provide support for automating the major activities in the testing process. The main advantage of a framework is

* Increased Productivity
* Easy and Reduced maintenance effort
* Consistent automation development across projects
* Process driven than person driven approach
* Controlled maintenance of automation artifacts

There is a range of automation testing tools available. Some of them are licensed and few others are open sourced. QTP, Cucumber, Capybara and other tools<ref>http://en.wikipedia.org/wiki/List_of_web_testing_tools</ref>

=='''Description'''==
Although HP UFT is usually used for UI based Test Case Automation, it can also automate some non-UI based test cases like database testing, webservice testing and file based operations. It offers a graphical user interface, keyboard support, multiple testing views, and scripting language.
<ref>http://www.softwaretestinghelp.com/qtp-quicktest-professional-tutorial-1/</ref>
===Data Driven Testing===
HP Unified Functional Testing supports data-driven testing. For example, data can be output to a data table for reuse elsewhere. [http://en.wikipedia.org/wiki/Data-driven_testing Data-driven testing] is implemented as a Microsoft Excel workbook that can be accessed from HP Unified Functional Testing. HP Unified Functional Testing has two types of data tables: the Global data sheet and Action (local) data sheets. The test steps can read data from these data tables in order to drive variable data into the application under test, and verify the expected result.<ref>http://www.qtp10.com/2009/07/using-global-and-action-data-sheets-in.html</ref>

===Views===
HP Unified Functional Testing provides two views—and ways to modify—a test script: Keyword View and Expert View. These views enable HP Unified Functional Testing to act as an Integrated Development Environment (IDE) for the test, and HP Unified Functional Testing includes many standard IDE features, such as breakpoints to pause a test at predetermined places.<ref>http://en.wikipedia.org/wiki/HP_QuickTest_Professional</ref>

====Keyword view====
Keyword View lets users create and view the steps of a test in a modular, table format. In Keyword View, users can also view properties for items such as checkpoints, output values, and actions, use conditional and loop statements, and insert breakpoints to assist in debugging a test.<ref>http://www.qtp10.com/2009/07/working-with-keyword-view-in-hp-qtp.html</ref>

====Expert View====
Expert view displays test code using [http://en.wikipedia.org/wiki/VBScript VBScript]. Designed for more advanced users, users can edit all test actions except for the root Global action, and changes are synchronized with the Keyword View.<ref>http://www.fdscallcentre.com/homepage/data/mi/DS-0413-020_QTPro6.0.pdf</ref>

===Scripting===
HP UFT's VBScript allows for classes, but not other object oriented properties such as inheritance and polymorphism. It also lacks a debugger, however UFT has a debugger provided by HP. Some Windows script ([http://en.wikipedia.org/wiki/Windows_Script_Host WScript],[http://en.wikipedia.org/wiki/WSH WSH],[http://en.wikipedia.org/wiki/Wmii WMI]) & [http://en.wikipedia.org/wiki/Visual_Basic_.NET VB.Net] code can be used in a script in the expert view <ref>https://h20546.www2.hp.com/main/training/course_details.cfm?Course=00008165&sitepick=US</ref>

===Exception handling===
Application crashes, Unexpected events and errors during a run session can disrupt the run session and distort results. This is a problem particularly when tests run unattended—the test pauses until one performs the operation needed to recover. To handle such situations, Error and Exception Handling is must while developing script or Automation Framework.<ref>http://qtpautomationcodes.blogspot.com/2013/05/error-handling-in-qtp.html</ref>
Error and Exception handling in HP UFT can be done by the following ways:

* [http://www.softwaretestinghelp.com/conditional-loop-statements-qtp-tutorial-4/ Conditional Statement]
* [http://www.tutorialspoint.com/qtp/qtp_error_handling.htm On Error statement]
* [http://www.tutorialspoint.com/qtp/qtp_recovery_scenarios.htm Recovery Scenarios]

=='''Life Cycle'''==
[[File:LifeCycle.jpg‎]]

=='''Comparison to other tools'''==
Tools such as [http://en.wikipedia.org/wiki/Cucumber_(software) Cucumber] and [http://rubygems.org/gems/capybara Capybara] run tests from the perspective of the user. Cucumber converts user stories into tests and Capybara simulates a user or web browser. Unified Functional Testing is used by programmers to preform specific test cases they code themselves.<ref>''Engineering Long-Lasting Software: An Agile Approach Using SaaS and Cloud Computing'', Beta Edition 0.9.0 by Armando Fox and David Patterson, August 23, 2012, p136, </ref>

'''Capybara''' interacts with a website the way a human would (like visiting a url, clicking a link, typing text into a form and submitting it). It is used to emulate a user's flow through a website. Test cases in Capybara will look like this:<ref>http://stackoverflow.com/questions/15004918/cucumber-vs-capybara</ref>
<pre>
describe "the signup process", :type => :feature do
before :each do
User.make(:email => 'user@example.com', :password => 'caplin')
end
it "signs me in" do
visit '/sessions/new'
within("#session") do
fill_in 'Login', :with => 'user@example.com'
fill_in 'Password', :with => 'password'
end
click_link 'Sign in'
page.should have_content 'Success'
end
end</pre>

'''Cucumber''' writes human-readable tests that are mapped onto code. With it, you can rewrite the above example like this:<ref>http://stackoverflow.com/questions/15004918/cucumber-vs-capybara</ref>

<pre>
Scenario: Signup process
Given a user exists with email "user@example.com" and password "caplin"
When I try to login with "user@example.com" and "caplin"
Then I should be logged in successfully
</pre>

[http://en.wikipedia.org/wiki/Selenium Selenium] is a tool for automating web applications for testing purposes.

'''Comparison of UFT with other tools'''<ref>http://www.aspiresys.com/WhitePapers/QTPvsSelenium.pdf</ref>
{| border="1" class="wikitable"
|+
! Feature
! UFT
! Selenium
! Cucumber/ Capybara
|-
! Windows (Non-browser)
based Application support
| Yes
| No
| No
|-
! Environment Support
| Only Windows
| Windows , Linux , Solaris
OS X , Others
| Windows , Linux , Solaris
OS X , Others
|-
! Windows (Non-browser)
based Application support
| Yes
| No
| No
|-
!Software Cost
| License & Annual maintenance Fees
| Zero
| Zero
|-
!Coding Experience of
Engineer
|Not Much
|Should be very good along with
technical capabilities of integrating
different pieces of framework
|Requires minimal use of Ruby programming
|-
!Script Creation Time
|Low
|High
|Medium
|-
!Hardware resource (CPU
+ RAM) consumption during
script execution
|High
|Low
|Low
|-
!Product Support
|Dedicate HP support along with
support forums
|Open Source Community
|Open Source Community
|-
!Framework
|Easily integrated with [http://en.wikipedia.org/wiki/HP_Quality_Center HP Quality Center] or [http://en.wikipedia.org/wiki/HP_Application_Lifecycle_Management HP ALM]
|Selenium + Eclipse + Maven / ANT
+ Jenkins / Hudson & its plugins /
Cruise Control + TestNG + SVN
|Ruby on Rails
Merb

Sinatra
|-
!Continuous Integration
|Possible through Quality Center
/ ALM or Jenkins
|Possible through Jenkins / Hudson
/ Cruise Control
|Possible through Rake, Ant, Maven and JUnit output
|}

=='''Disadvantages'''==
UFT market is shrinking slowly.<ref>http://www.quora.com/Is-there-demand-for-QTP</ref> It is being used more in legacy application and tools like Selenium, Cucumber and Capybara are becoming more popular.

One of the main reason that we move from UFT is that it is a reactive approach of writing test automation. The product is finished and the tester starts writing the automation test. Only the tester writes the automation. With cucumber and selenium, writing automation test is a joint effort between the developers and the testers. The testers write the test cases in cucumber scenario format, then the developers write the steps definition. This way, everyone is contributing and everyone is reviewing the test cases. Cucumber code is readable and easy to understand.<ref>http://qastuffs.blogspot.com/2010_12_01_archive.html</ref>

Unified Functional Testing is developed mainly for Windows based systems and it relies on outdated Windows tools like VBXScript. Tests can not be run outside of the UFT environment nor are they compatible with all browser types.<ref>http://www8.hp.com/us/en/software-solutions/unified-functional-testing-automated-testing/demos-documents.html#!&pd1=1</ref>

=='''References'''==
<references/>

CSC/ECE 517 Fall 2014/ch1a 22 as

2014-09-16T01:52:22Z

Abora:

'''HP Unified Functional Testing Professional'''

HP Unified Functional Testing (UFT) software, formerly known as HP Quick Test Professional (QTP),<ref>http://www.automationrepository.com/2012/12/hp-unified-functional-testing-uft-11-5-new-features</ref> provides [http://en.wikipedia.org/wiki/Functional_testing functional testing] and [http://en.wikipedia.org/wiki/Regression_testing regression testing] automation for software applications and environments.<ref>http://www8.hp.com/us/en/software-solutions/application-lifecycle-management-application-test-software/index.html?zn=bto&cp=1-11-127-24^1352_4000_1__</ref> HP Unified Functional Testing can be used for enterprise [http://en.wikipedia.org/wiki/Quality_assurance quality assurance].<ref>http://www.learnqtp.com/qtp-quality-center-test-director-guide/</ref> HP Unified Functional Testing is a test automation tool originally developed by [http://en.wikipedia.org/wiki/Mercury_Interactive Mercury Interactive] and later acquired by [http://en.wikipedia.org/wiki/Hewlett-Packard Hewlett Packard].<ref> http://www.devbistro.com/articles/Testing/Mercury-QuickTest-Professional-Evaluation</ref> HP Unified Functional Testing 11.5 combined HP QuickTest Professional and HP Service Test into a single software package,<ref> http://selftechy.com/2013/10/07/hp-uft-11-50-unified-functional-testing</ref> which is currently available from the HP Software Division. The integrated HP Unified Functional Testing software allows developers to test from a single console all three layers of a program’s operations: the interface, [http://en.wikipedia.org/wiki/Service_layer the service layer] and the database layer.<ref>http://www.computerworld.com/article/2493313/data-center/hp-simplifies-automated-software-testing-suite.html</ref>

[https://docs.google.com/document/d/1eq3XHiUUBIrEBx-R2Mgolaw7HttSgzPniwDLEF5oVk0/edit# Writeup page.]
{| align=right style="border: 1px solid gray;" class="wikitable"
|+ HP Uniffied Functional Testing<ref>http://en.wikipedia.org/wiki/HP_QuickTest_Professional</ref>
|-
| [http://en.wikipedia.org/wiki/Software_developer? Developer(s)] || [http://en.wikipedia.org/wiki/Hewlett-Packard? HP], [http://en.wikipedia.org/wiki/HP_Software_Division? HP Software Division]
|-
| [http://en.wikipedia.org/wiki/Software_release_life_cycle? Stable release] || 12.01
|-
| [http://en.wikipedia.org/wiki/Operating_system? Operating system] || [http://en.wikipedia.org/wiki/Microsoft_Windows? Microsoft Windows]
|-
| [http://en.wikipedia.org/wiki/List_of_software_categories? Type] || [http://en.wikipedia.org/wiki/Test_automation? Test automation tools]
|-
| [http://en.wikipedia.org/wiki/Software_license? License] || [http://en.wikipedia.org/wiki/Proprietary_software? Proprietary]
|}

=='''Background'''==
Test automation is the use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions.<ref>''The Testing Network, An Integral Approach to Test Activities in Large Software Projects'' by Jean-Jacques Pierre Henry (Aug 17, 2008), p413, ISBN 978-3-540-78504-0</ref> Test Automation is a development discipline as it uses scripting languages to instruct the tool how to interact with your application. As such careful consideration needs to be paid to

* Exception handling for bugs that occur during testing cycles(i.e, unexpected error messages during a test run).
* How the tool synchronizes with your application(e.g. if there are slow response times from your environment)
* The level of maintenance required to keep the tests up to date with changes in the application [http://en.wikipedia.org/wiki/Graphical_user_interface GUI](i.e, new buttons, data fields, custom controls etc)

Any test automation framework is a set of assumptions, concepts and tools that provide support for automating the major activities in the testing process. The main advantage of a framework is

* Increased Productivity
* Easy and Reduced maintenance effort
* Consistent automation development across projects
* Process driven than person driven approach
* Controlled maintenance of automation artifacts

There is a range of automation testing tools available. Some of them are licensed and few others are open sourced. QTP, Cucumber, Capybara and other tools<ref>http://en.wikipedia.org/wiki/List_of_web_testing_tools</ref>

=='''Description'''==
Although HP UFT is usually used for UI based Test Case Automation, it can also automate some non-UI based test cases like database testing, webservice testing and file based operations. It offers a graphical user interface, keyboard support, multiple testing views, and scripting language.
<ref>http://www.softwaretestinghelp.com/qtp-quicktest-professional-tutorial-1/</ref>
===Data Driven Testing===
HP Unified Functional Testing supports data-driven testing. For example, data can be output to a data table for reuse elsewhere. [http://en.wikipedia.org/wiki/Data-driven_testing Data-driven testing] is implemented as a Microsoft Excel workbook that can be accessed from HP Unified Functional Testing. HP Unified Functional Testing has two types of data tables: the Global data sheet and Action (local) data sheets. The test steps can read data from these data tables in order to drive variable data into the application under test, and verify the expected result.<ref>http://www.qtp10.com/2009/07/using-global-and-action-data-sheets-in.html</ref>

===Views===
HP Unified Functional Testing provides two views—and ways to modify—a test script: Keyword View and Expert View. These views enable HP Unified Functional Testing to act as an Integrated Development Environment (IDE) for the test, and HP Unified Functional Testing includes many standard IDE features, such as breakpoints to pause a test at predetermined places.<ref>http://en.wikipedia.org/wiki/HP_QuickTest_Professional</ref>

====Keyword view====
Keyword View lets users create and view the steps of a test in a modular, table format. In Keyword View, users can also view properties for items such as checkpoints, output values, and actions, use conditional and loop statements, and insert breakpoints to assist in debugging a test.<ref>http://www.qtp10.com/2009/07/working-with-keyword-view-in-hp-qtp.html</ref>

====Expert View====
Expert view displays test code using [http://en.wikipedia.org/wiki/VBScript VBScript]. Designed for more advanced users, users can edit all test actions except for the root Global action, and changes are synchronized with the Keyword View.<ref>http://www.fdscallcentre.com/homepage/data/mi/DS-0413-020_QTPro6.0.pdf</ref>

===Scripting===
HP UFT's VBScript allows for classes, but not other object oriented properties such as inheritance and polymorphism. It also lacks a debugger, however UFT has a debugger provided by HP. Some Windows script ([http://en.wikipedia.org/wiki/Windows_Script_Host WScript],[http://en.wikipedia.org/wiki/WSH WSH],[http://en.wikipedia.org/wiki/Wmii WMI]) & [http://en.wikipedia.org/wiki/Visual_Basic_.NET VB.Net] code can be used in a script in the expert view <ref>https://h20546.www2.hp.com/main/training/course_details.cfm?Course=00008165&sitepick=US</ref>

===Exception handling===
Application crashes, Unexpected events and errors during a run session can disrupt the run session and distort results. This is a problem particularly when tests run unattended—the test pauses until one performs the operation needed to recover. To handle such situations, Error and Exception Handling is must while developing script or Automation Framework.<ref>http://qtpautomationcodes.blogspot.com/2013/05/error-handling-in-qtp.html</ref>
Error and Exception handling in HP UFT can be done by the following ways:

* Conditional Statement
* On Error statement
* Recovery Scenarios

=='''Life Cycle'''==
[[File:LifeCycle.jpg‎]]

=='''Comparison to other tools'''==
Tools such as [http://en.wikipedia.org/wiki/Cucumber_(software) Cucumber] and [https://rubygems.org/gems/capybara Capybara] run tests from the perspective of the user. Cucumber converts user stories into tests and Capybara simulates a user or web browser. Unified Functional Testing is used by programmers to preform specific test cases they code themselves.<ref>''Engineering Long-Lasting Software: An Agile Approach Using SaaS and Cloud Computing'', Beta Edition 0.9.0 by Armando Fox and David Patterson, August 23, 2012, p136, </ref>

'''Capybara''' interacts with a website the way a human would (like visiting a url, clicking a link, typing text into a form and submitting it). It is used to emulate a user's flow through a website. Test cases in Capybara will look like this:<ref>http://stackoverflow.com/questions/15004918/cucumber-vs-capybara</ref>
<pre>
describe "the signup process", :type => :feature do
before :each do
User.make(:email => 'user@example.com', :password => 'caplin')
end
it "signs me in" do
visit '/sessions/new'
within("#session") do
fill_in 'Login', :with => 'user@example.com'
fill_in 'Password', :with => 'password'
end
click_link 'Sign in'
page.should have_content 'Success'
end
end</pre>

'''Cucumber''' writes human-readable tests that are mapped onto code. With it, you can rewrite the above example like this:<ref>http://stackoverflow.com/questions/15004918/cucumber-vs-capybara</ref>

<pre>
Scenario: Signup process
Given a user exists with email "user@example.com" and password "caplin"
When I try to login with "user@example.com" and "caplin"
Then I should be logged in successfully
</pre>

[http://en.wikipedia.org/wiki/Selenium Selenium] is a tool for automating web applications for testing purposes.

'''Comparison of UFT with other tools'''<ref>http://www.aspiresys.com/WhitePapers/QTPvsSelenium.pdf</ref>
{| border="1" class="wikitable"
|+
! Feature
! UFT
! Selenium
! Cucumber/ Capybara
|-
! Windows (Non-browser)
based Application support
| Yes
| No
| No
|-
! Environment Support
| Only Windows
| Windows , Linux , Solaris
OS X , Others
| Windows , Linux , Solaris
OS X , Others
|-
! Windows (Non-browser)
based Application support
| Yes
| No
| No
|-
!Software Cost
| License & Annual maintenance Fees
| Zero
| Zero
|-
!Coding Experience of
Engineer
|Not Much
|Should be very good along with
technical capabilities of integrating
different pieces of framework
|Requires minimal use of Ruby programming
|-
!Script Creation Time
|Low
|High
|Medium
|-
!Hardware resource (CPU
+ RAM) consumption during
script execution
|High
|Low
|Low
|-
!Product Support
|Dedicate HP support along with
support forums
|Open Source Community
|Open Source Community
|-
!Framework
|Easily integrated with [http://en.wikipedia.org/wiki/HP_Quality_Center HP Quality Center] or [http://en.wikipedia.org/wiki/HP_Application_Lifecycle_Management HP ALM]
|Selenium + Eclipse + Maven / ANT
+ Jenkins / Hudson & its plugins /
Cruise Control + TestNG + SVN
|Ruby on Rails
Merb

Sinatra
|-
!Continuous Integration
|Possible through Quality Center
/ ALM or Jenkins
|Possible through Jenkins / Hudson
/ Cruise Control
|Possible through Rake, Ant, Maven and JUnit output
|}

=='''Disadvantages'''==
UFT market is shrinking slowly.<ref>http://www.quora.com/Is-there-demand-for-QTP</ref> It is being used more in legacy application and tools like Selenium, Cucumber and Capybara are becoming more popular.

One of the main reason that we move from UFT is that it is a reactive approach of writing test automation. The product is finished and the tester starts writing the automation test. Only the tester writes the automation. With cucumber and selenium, writing automation test is a joint effort between the developers and the testers. The testers write the test cases in cucumber scenario format, then the developers write the steps definition. This way, everyone is contributing and everyone is reviewing the test cases. Cucumber code is readable and easy to understand.<ref>http://qastuffs.blogspot.com/2010_12_01_archive.html</ref>

Unified Functional Testing is developed mainly for Windows based systems and it relies on outdated Windows tools like VBXScript. Tests can not be run outside of the UFT environment nor are they compatible with all browser types.<ref>http://www8.hp.com/us/en/software-solutions/unified-functional-testing-automated-testing/demos-documents.html#!&pd1=1</ref>

=='''References'''==
<references/>

CSC/ECE 517 Fall 2014/ch1a 22 as

2014-09-16T01:45:24Z

Abora:

'''HP Unified Functional Testing Professional'''

HP Unified Functional Testing (UFT) software, formerly known as HP Quick Test Professional (QTP),<ref>http://www.automationrepository.com/2012/12/hp-unified-functional-testing-uft-11-5-new-features</ref> provides [http://en.wikipedia.org/wiki/Functional_testing functional testing] and [http://en.wikipedia.org/wiki/Regression_testing regression testing] automation for software applications and environments.<ref>http://www8.hp.com/us/en/software-solutions/application-lifecycle-management-application-test-software/index.html?zn=bto&cp=1-11-127-24^1352_4000_1__</ref> HP Unified Functional Testing can be used for enterprise [http://en.wikipedia.org/wiki/Quality_assurance quality assurance].<ref>http://www.learnqtp.com/qtp-quality-center-test-director-guide/</ref> HP Unified Functional Testing is a test automation tool originally developed by [http://en.wikipedia.org/wiki/Mercury_Interactive Mercury Interactive] and later acquired by [http://en.wikipedia.org/wiki/Hewlett-Packard Hewlett Packard].<ref> http://www.devbistro.com/articles/Testing/Mercury-QuickTest-Professional-Evaluation</ref> HP Unified Functional Testing 11.5 combined HP QuickTest Professional and HP Service Test into a single software package,<ref> http://selftechy.com/2013/10/07/hp-uft-11-50-unified-functional-testing</ref> which is currently available from the HP Software Division. The integrated HP Unified Functional Testing software allows developers to test from a single console all three layers of a program’s operations: the interface, [http://en.wikipedia.org/wiki/Service_layer the service layer] and the database layer.<ref>http://www.computerworld.com/article/2493313/data-center/hp-simplifies-automated-software-testing-suite.html</ref>

[https://docs.google.com/document/d/1eq3XHiUUBIrEBx-R2Mgolaw7HttSgzPniwDLEF5oVk0/edit# Writeup page.]
{| align=right style="border: 1px solid gray;" class="wikitable"
|+ HP Uniffied Functional Testing<ref>http://en.wikipedia.org/wiki/HP_QuickTest_Professional</ref>
|-
| [http://en.wikipedia.org/wiki/Software_developer? Developer(s)] || [http://en.wikipedia.org/wiki/Hewlett-Packard? HP], [http://en.wikipedia.org/wiki/HP_Software_Division? HP Software Division]
|-
| [http://en.wikipedia.org/wiki/Software_release_life_cycle? Stable release] || 12.01
|-
| [http://en.wikipedia.org/wiki/Operating_system? Operating system] || [http://en.wikipedia.org/wiki/Microsoft_Windows? Microsoft Windows]
|-
| [http://en.wikipedia.org/wiki/List_of_software_categories? Type] || [http://en.wikipedia.org/wiki/Test_automation? Test automation tools]
|-
| [http://en.wikipedia.org/wiki/Software_license? License] || [http://en.wikipedia.org/wiki/Proprietary_software? Proprietary]
|}

=='''Background'''==
Test automation is the use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions.<ref>''The Testing Network, An Integral Approach to Test Activities in Large Software Projects'' by Jean-Jacques Pierre Henry (Aug 17, 2008), p413, ISBN 978-3-540-78504-0</ref> Test Automation is a development discipline as it uses scripting languages to instruct the tool how to interact with your application. As such careful consideration needs to be paid to

* Exception handling for bugs that occur during testing cycles(i.e, unexpected error messages during a test run).
* How the tool synchronizes with your application(e.g. if there are slow response times from your environment)
* The level of maintenance required to keep the tests up to date with changes in the application [http://en.wikipedia.org/wiki/Graphical_user_interface GUI](i.e, new buttons, data fields, custom controls etc)

Any test automation framework is a set of assumptions, concepts and tools that provide support for automating the major activities in the testing process. The main advantage of a framework is

* Increased Productivity
* Easy and Reduced maintenance effort
* Consistent automation development across projects
* Process driven than person driven approach
* Controlled maintenance of automation artifacts

There is a range of automation testing tools available. Some of them are licensed and few others are open sourced. QTP, Cucumber, Capybara and other tools<ref>http://en.wikipedia.org/wiki/List_of_web_testing_tools</ref>

=='''Description'''==
Although HP UFT is usually used for UI based Test Case Automation, it can also automate some non-UI based test cases like database testing, webservice testing and file based operations. It offers a graphical user interface, keyboard support, multiple testing views, and scripting language.
<ref>http://www.softwaretestinghelp.com/qtp-quicktest-professional-tutorial-1/</ref>
===Data Driven Testing===
HP Unified Functional Testing supports data-driven testing. For example, data can be output to a data table for reuse elsewhere. [http://en.wikipedia.org/wiki/Data-driven_testing Data-driven testing] is implemented as a Microsoft Excel workbook that can be accessed from HP Unified Functional Testing. HP Unified Functional Testing has two types of data tables: the Global data sheet and Action (local) data sheets. The test steps can read data from these data tables in order to drive variable data into the application under test, and verify the expected result.<ref>http://www.qtp10.com/2009/07/using-global-and-action-data-sheets-in.html</ref>

===Views===
HP Unified Functional Testing provides two views—and ways to modify—a test script: Keyword View and Expert View. These views enable HP Unified Functional Testing to act as an Integrated Development Environment (IDE) for the test, and HP Unified Functional Testing includes many standard IDE features, such as breakpoints to pause a test at predetermined places.<ref>http://en.wikipedia.org/wiki/HP_QuickTest_Professional</ref>

====Keyword view====
Keyword View lets users create and view the steps of a test in a modular, table format. In Keyword View, users can also view properties for items such as checkpoints, output values, and actions, use conditional and loop statements, and insert breakpoints to assist in debugging a test.<ref>http://www.qtp10.com/2009/07/working-with-keyword-view-in-hp-qtp.html</ref>

====Expert View====
Expert view displays test code using [http://en.wikipedia.org/wiki/VBScript VBScript]. Designed for more advanced users, users can edit all test actions except for the root Global action, and changes are synchronized with the Keyword View.<ref>http://www.fdscallcentre.com/homepage/data/mi/DS-0413-020_QTPro6.0.pdf</ref>

===Scripting===
HP UFT's VBScript allows for classes, but not other object oriented properties such as inheritance and polymorphism. It also lacks a debugger, however UFT has a debugger provided by HP. Some Windows script ([http://en.wikipedia.org/wiki/Windows_Script_Host WScript],[http://en.wikipedia.org/wiki/WSH WSH],[http://en.wikipedia.org/wiki/Wmii WMI]) & [http://en.wikipedia.org/wiki/Visual_Basic_.NET VB.Net] code can be used in a script in the expert view <ref>https://h20546.www2.hp.com/main/training/course_details.cfm?Course=00008165&sitepick=US</ref>

===Exception handling===
Application crashes, Unexpected events and errors during a run session can disrupt the run session and distort results. This is a problem particularly when tests run unattended—the test pauses until one performs the operation needed to recover. To handle such situations, Error and Exception Handling is must while developing script or Automation Framework.<ref>http://qtpautomationcodes.blogspot.com/2013/05/error-handling-in-qtp.html</ref>
Error and Exception handling in HP UFT can be done by the following ways:

* Conditional Statement
* On Error statement
* Recovery Scenarios

=='''Life Cycle'''==
[[File:LifeCycle.jpg‎]]

=='''Comparison to other tools'''==
Tools such as [http://en.wikipedia.org/wiki/Cucumber_(software) Cucumber] and [https://rubygems.org/gems/capybara Capybara] run tests from the perspective of the user. Cucumber converts user stories into tests and Capybara simulates a user or web browser. Unified Functional Testing is used by programmers to preform specific test cases they code themselves.<ref>''Engineering Long-Lasting Software: An Agile Approach Using SaaS and Cloud Computing'', Beta Edition 0.9.0 by Armando Fox and David Patterson, August 23, 2012, p136, </ref>

'''Capybara''' interacts with a website the way a human would (like visiting a url, clicking a link, typing text into a form and submitting it). It is used to emulate a user's flow through a website. Test cases in Capybara will look like this:<ref>http://stackoverflow.com/questions/15004918/cucumber-vs-capybara</ref>
<pre>
describe "the signup process", :type => :feature do
before :each do
User.make(:email => 'user@example.com', :password => 'caplin')
end
it "signs me in" do
visit '/sessions/new'
within("#session") do
fill_in 'Login', :with => 'user@example.com'
fill_in 'Password', :with => 'password'
end
click_link 'Sign in'
page.should have_content 'Success'
end
end</pre>

'''Cucumber''' writes human-readable tests that are mapped onto code. With it, you can rewrite the above example like this:<ref>http://stackoverflow.com/questions/15004918/cucumber-vs-capybara</ref>

<pre>
Scenario: Signup process
Given a user exists with email "user@example.com" and password "caplin"
When I try to login with "user@example.com" and "caplin"
Then I should be logged in successfully
</pre>

[http://en.wikipedia.org/wiki/Selenium Selenium] is a tool for automating web applications for testing purposes.

'''Comparison of UFT with other tools'''<ref>http://www.aspiresys.com/WhitePapers/QTPvsSelenium.pdf</ref>
{| border="1" class="wikitable"
|+
! Feature
! UFT
! Selenium
! Cucumber/ Capybara
|-
! Windows (Non-browser)
based Application support
| Yes
| No
| No
|-
! Environment Support
| Only Windows
| Windows , Linux , Solaris
OS X , Others
| Windows , Linux , Solaris
OS X , Others
|-
! Windows (Non-browser)
based Application support
| Yes
| No
| No
|-
!Software Cost
| License & Annual maintenance Fees
| Zero
| Zero
|-
!Coding Experience of
Engineer
|Not Much
|Should be very good along with
technical capabilities of integrating
different pieces of framework
|Requires minimal use of Ruby programming
|-
!Script Creation Time
|Low
|High
|Medium
|-
!Hardware resource (CPU
+ RAM) consumption during
script execution
|High
|Low
|Low
|-
!Product Support
|Dedicate HP support along with
support forums
|Open Source Community
|Open Source Community
|-
!Framework
|Easily integrated with HP Quality
Center or HP ALM
|Selenium + Eclipse + Maven / ANT
+ Jenkins / Hudson & its plugins /
Cruise Control + TestNG + SVN
|Ruby on Rails
Merb
Sinatra
|-
!Continuous Integration
|Possible through Quality Center
/ ALM or Jenkins
|Possible through Jenkins / Hudson
/ Cruise Control
|Possible through Rake, Ant, Maven and JUnit output
|}

=='''Disadvantages'''==
UFT market is shrinking slowly.<ref>http://www.quora.com/Is-there-demand-for-QTP</ref> It is being used more in legacy application and tools like Selenium, Cucumber and Capybara are becoming more popular.

One of the main reason that we move from UFT is that it is a reactive approach of writing test automation. The product is finished and the tester starts writing the automation test. Only the tester writes the automation. With cucumber and selenium, writing automation test is a joint effort between the developers and the testers. The testers write the test cases in cucumber scenario format, then the developers write the steps definition. This way, everyone is contributing and everyone is reviewing the test cases. Cucumber code is readable and easy to understand.<ref>http://qastuffs.blogspot.com/2010_12_01_archive.html</ref>

Unified Functional Testing is developed mainly for Windows based systems and it relies on outdated Windows tools like VBXScript. Tests can not be run outside of the UFT environment nor are they compatible with all browser types.<ref>http://www8.hp.com/us/en/software-solutions/unified-functional-testing-automated-testing/demos-documents.html#!&pd1=1</ref>

=='''References'''==
<references/>

CSC/ECE 517 Fall 2014/ch1a 22 as

2014-09-16T01:33:45Z

Abora:

'''HP Unified Functional Testing Professional'''

HP Unified Functional Testing (UFT) software, formerly known as HP Quick Test Professional (QTP),<ref>http://www.automationrepository.com/2012/12/hp-unified-functional-testing-uft-11-5-new-features</ref> provides [http://en.wikipedia.org/wiki/Functional_testing functional testing] and [http://en.wikipedia.org/wiki/Regression_testing regression testing] automation for software applications and environments.<ref>http://www8.hp.com/us/en/software-solutions/application-lifecycle-management-application-test-software/index.html?zn=bto&cp=1-11-127-24^1352_4000_1__</ref> HP Unified Functional Testing can be used for enterprise [http://en.wikipedia.org/wiki/Quality_assurance quality assurance].<ref>http://www.learnqtp.com/qtp-quality-center-test-director-guide/</ref> HP Unified Functional Testing is a test automation tool originally developed by [http://en.wikipedia.org/wiki/Mercury_Interactive Mercury Interactive] and later acquired by [http://en.wikipedia.org/wiki/Hewlett-Packard Hewlett Packard].<ref> http://www.devbistro.com/articles/Testing/Mercury-QuickTest-Professional-Evaluation</ref> HP Unified Functional Testing 11.5 combined HP QuickTest Professional and HP Service Test into a single software package,<ref> http://selftechy.com/2013/10/07/hp-uft-11-50-unified-functional-testing</ref> which is currently available from the HP Software Division. The integrated HP Unified Functional Testing software allows developers to test from a single console all three layers of a program’s operations: the interface, [http://en.wikipedia.org/wiki/Service_layer the service layer] and the database layer.<ref>http://www.computerworld.com/article/2493313/data-center/hp-simplifies-automated-software-testing-suite.html</ref>

[https://docs.google.com/document/d/1eq3XHiUUBIrEBx-R2Mgolaw7HttSgzPniwDLEF5oVk0/edit# Writeup page.]
{| align=right style="border: 1px solid gray;" class="wikitable"
|+ HP Uniffied Functional Testing<ref>http://en.wikipedia.org/wiki/HP_QuickTest_Professional</ref>
|-
| [http://en.wikipedia.org/wiki/Software_developer? Developer(s)] || [http://en.wikipedia.org/wiki/Hewlett-Packard? HP], [http://en.wikipedia.org/wiki/HP_Software_Division? HP Software Division]
|-
| [http://en.wikipedia.org/wiki/Software_release_life_cycle? Stable release] || 12.01
|-
| [http://en.wikipedia.org/wiki/Operating_system? Operating system] || [http://en.wikipedia.org/wiki/Microsoft_Windows? Microsoft Windows]
|-
| [http://en.wikipedia.org/wiki/List_of_software_categories? Type] || [http://en.wikipedia.org/wiki/Test_automation? Test automation tools]
|-
| [http://en.wikipedia.org/wiki/Software_license? License] || [http://en.wikipedia.org/wiki/Proprietary_software? Proprietary]
|}

=='''Background'''==
Test automation is the use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions.<ref>''The Testing Network, An Integral Approach to Test Activities in Large Software Projects'' by Jean-Jacques Pierre Henry (Aug 17, 2008), p413, ISBN 978-3-540-78504-0</ref> Test Automation is a development discipline as it uses scripting languages to instruct the tool how to interact with your application. As such careful consideration needs to be paid to

* Exception handling for bugs that occur during testing cycles(i.e, unexpected error messages during a test run).
* How the tool synchronizes with your application(e.g. if there are slow response times from your environment)
* The level of maintenance required to keep the tests up to date with changes in the application [http://en.wikipedia.org/wiki/Graphical_user_interface GUI](i.e, new buttons, data fields, custom controls etc)

Any test automation framework is a set of assumptions, concepts and tools that provide support for automating the major activities in the testing process. The main advantage of a framework is

* Increased Productivity
* Easy and Reduced maintenance effort
* Consistent automation development across projects
* Process driven than person driven approach
* Controlled maintenance of automation artifacts

There is a range of automation testing tools available. Some of them are licensed and few others are open sourced. QTP, Cucumber, Capybara and other tools<ref>http://en.wikipedia.org/wiki/List_of_web_testing_tools</ref>

=='''Description'''==
Although HP UFT is usually used for UI based Test Case Automation, it can also automate some non-UI based test cases like database testing, webservice testing and file based operations. It offers a graphical user interface, keyboard support, multiple testing views, and scripting language.
<ref>http://www.softwaretestinghelp.com/qtp-quicktest-professional-tutorial-1/</ref>
===Data Driven Testing===
HP Unified Functional Testing supports data-driven testing. For example, data can be output to a data table for reuse elsewhere. [http://en.wikipedia.org/wiki/Data-driven_testing Data-driven testing] is implemented as a Microsoft Excel workbook that can be accessed from HP Unified Functional Testing. HP Unified Functional Testing has two types of data tables: the Global data sheet and Action (local) data sheets. The test steps can read data from these data tables in order to drive variable data into the application under test, and verify the expected result.<ref>http://www.qtp10.com/2009/07/using-global-and-action-data-sheets-in.html</ref>

===Views===
HP Unified Functional Testing provides two views—and ways to modify—a test script: Keyword View and Expert View. These views enable HP Unified Functional Testing to act as an Integrated Development Environment (IDE) for the test, and HP Unified Functional Testing includes many standard IDE features, such as breakpoints to pause a test at predetermined places.<ref>http://en.wikipedia.org/wiki/HP_QuickTest_Professional</ref>

====Keyword view====
Keyword View lets users create and view the steps of a test in a modular, table format. In Keyword View, users can also view properties for items such as checkpoints, output values, and actions, use conditional and loop statements, and insert breakpoints to assist in debugging a test.<ref>http://www.qtp10.com/2009/07/working-with-keyword-view-in-hp-qtp.html</ref>

====Expert View====
Expert view displays test code using [http://en.wikipedia.org/wiki/VBScript VBScript]. Designed for more advanced users, users can edit all test actions except for the root Global action, and changes are synchronized with the Keyword View.<ref>http://www.fdscallcentre.com/homepage/data/mi/DS-0413-020_QTPro6.0.pdf</ref>

===Scripting===
HP UFT's VBScript allows for classes, but not other object oriented properties such as inheritance and polymorphism. It also lacks a debugger, however UFT has a debugger provided by HP. Some Windows script (WScript,WSH,WMI) & VB.Net code can be used in a script in the expert view <ref>https://h20546.www2.hp.com/main/training/course_details.cfm?Course=00008165&sitepick=US</ref>

===Exception handling===
Application crashes, Unexpected events and errors during a run session can disrupt the run session and distort results. This is a problem particularly when tests run unattended—the test pauses until one performs the operation needed to recover. To handle such situations, Error and Exception Handling is must while developing script or Automation Framework.<ref>http://qtpautomationcodes.blogspot.com/2013/05/error-handling-in-qtp.html</ref>
Error and Exception handling in HP UFT can be done by the following ways:

* Conditional Statement
* On Error statement
* Recovery Scenarios

=='''Life Cycle'''==
[[File:LifeCycle.jpg‎]]

=='''Comparison to other tools'''==
Tools such as Cucumber and Capybara run tests from the perspective of the user. Cucumber converts user stories into tests and Capybara simulates a user or web browser. Unified Functional Testing is used by programmers to preform specific test cases they code themselves.<ref>''Engineering Long-Lasting Software: An Agile Approach Using SaaS and Cloud Computing'', Beta Edition 0.9.0 by Armando Fox and David Patterson, August 23, 2012, p136, </ref>

'''Capybara''' interacts with a website the way a human would (like visiting a url, clicking a link, typing text into a form and submitting it). It is used to emulate a user's flow through a website. Test cases in Capybara will look like this:<ref>http://stackoverflow.com/questions/15004918/cucumber-vs-capybara</ref>
<pre>
describe "the signup process", :type => :feature do
before :each do
User.make(:email => 'user@example.com', :password => 'caplin')
end
it "signs me in" do
visit '/sessions/new'
within("#session") do
fill_in 'Login', :with => 'user@example.com'
fill_in 'Password', :with => 'password'
end
click_link 'Sign in'
page.should have_content 'Success'
end
end</pre>

'''Cucumber''' writes human-readable tests that are mapped onto code. With it, you can rewrite the above example like this:<ref>http://stackoverflow.com/questions/15004918/cucumber-vs-capybara</ref>

<pre>
Scenario: Signup process
Given a user exists with email "user@example.com" and password "caplin"
When I try to login with "user@example.com" and "caplin"
Then I should be logged in successfully
</pre>

'''Selenium''' is a tool for automating web applications for testing purposes.

'''Comparison of UFT with other tools'''<ref>http://www.aspiresys.com/WhitePapers/QTPvsSelenium.pdf</ref>
{| border="1" class="wikitable"
|+
! Feature
! UFT
! Selenium
! Cucumber/ Capybara
|-
! Windows (Non-browser)
based Application support
| Yes
| No
| No
|-
! Environment Support
| Only Windows
| Windows , Linux , Solaris
OS X , Others
| Windows , Linux , Solaris
OS X , Others
|-
! Windows (Non-browser)
based Application support
| Yes
| No
| No
|-
!Software Cost
| License & Annual maintenance Fees
| Zero
| Zero
|-
!Coding Experience of
Engineer
|Not Much
|Should be very good along with
technical capabilities of integrating
different pieces of framework
|Requires minimal use of Ruby programming
|-
!Script Creation Time
|Low
|High
|Medium
|-
!Hardware resource (CPU
+ RAM) consumption during
script execution
|High
|Low
|Low
|-
!Product Support
|Dedicate HP support along with
support forums
|Open Source Community
|Open Source Community
|-
!Framework
|Easily integrated with HP Quality
Center or HP ALM
|Selenium + Eclipse + Maven / ANT
+ Jenkins / Hudson & its plugins /
Cruise Control + TestNG + SVN
|Ruby on Rails
Merb
Sinatra
|-
!Continuous Integration
|Possible through Quality Center
/ ALM or Jenkins
|Possible through Jenkins / Hudson
/ Cruise Control
|Possible through Rake, Ant, Maven and JUnit output
|}

=='''Disadvantages'''==
Unified Functional Testing is developed mainly for Windows based systems and it relies on outdated Windows tools like VBXScript. Tests can not be run outside of the UFT environment nor are they compatible with all browser types.<ref>http://www8.hp.com/us/en/software-solutions/unified-functional-testing-automated-testing/demos-documents.html#!&pd1=1</ref>

=='''References'''==
<references/>

CSC/ECE 517 Fall 2014/ch1a 22 as

2014-09-16T01:33:22Z

Abora:

'''HP Unified Functional Testing Professional'''

HP Unified Functional Testing (UFT) software, formerly known as HP Quick Test Professional (QTP),<ref>http://www.automationrepository.com/2012/12/hp-unified-functional-testing-uft-11-5-new-features</ref> provides [http://en.wikipedia.org/wiki/Functional_testing functional testing] and [http://en.wikipedia.org/wiki/Regression_testing regression testing] automation for software applications and environments.<ref>http://www8.hp.com/us/en/software-solutions/application-lifecycle-management-application-test-software/index.html?zn=bto&cp=1-11-127-24^1352_4000_1__</ref> HP Unified Functional Testing can be used for enterprise [http://en.wikipedia.org/wiki/Quality_assurance quality assurance].<ref>http://www.learnqtp.com/qtp-quality-center-test-director-guide/</ref> HP Unified Functional Testing is a test automation tool originally developed by [http://en.wikipedia.org/wiki/Mercury_Interactive Mercury Interactive] and later acquired by [http://en.wikipedia.org/wiki/Hewlett-Packard Hewlett Packard].<ref> http://www.devbistro.com/articles/Testing/Mercury-QuickTest-Professional-Evaluation</ref> HP Unified Functional Testing 11.5 combined HP QuickTest Professional and HP Service Test into a single software package,<ref> http://selftechy.com/2013/10/07/hp-uft-11-50-unified-functional-testing</ref> which is currently available from the HP Software Division. The integrated HP Unified Functional Testing software allows developers to test from a single console all three layers of a program’s operations: the interface, [http://en.wikipedia.org/wiki/Service_layer the service layer] and the database layer.<ref>http://www.computerworld.com/article/2493313/data-center/hp-simplifies-automated-software-testing-suite.html</ref>

[https://docs.google.com/document/d/1eq3XHiUUBIrEBx-R2Mgolaw7HttSgzPniwDLEF5oVk0/edit# Writeup page.]
{| align=right style="border: 1px solid gray;" class="wikitable"
|+ HP Unified Functional Testing<ref>http://en.wikipedia.org/wiki/HP_QuickTest_Professional</ref>
|-
| [http://en.wikipedia.org/wiki/Software_developer? Developer(s)] || [http://en.wikipedia.org/wiki/Hewlett-Packard? HP], [http://en.wikipedia.org/wiki/HP_Software_Division? HP Software Division]
|-
| [http://en.wikipedia.org/wiki/Software_release_life_cycle? Stable release] || 12.01
|-
| [http://en.wikipedia.org/wiki/Operating_system? Operating system] || [http://en.wikipedia.org/wiki/Microsoft_Windows? Microsoft Windows]
|-
| [http://en.wikipedia.org/wiki/List_of_software_categories? Type] || [http://en.wikipedia.org/wiki/Test_automation? Test automation tools]
|-
| [http://en.wikipedia.org/wiki/Software_license? License] || [http://en.wikipedia.org/wiki/Proprietary_software? Proprietary]
|}

=='''Background'''==
Test automation is the use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions.<ref>''The Testing Network, An Integral Approach to Test Activities in Large Software Projects'' by Jean-Jacques Pierre Henry (Aug 17, 2008), p413, ISBN 978-3-540-78504-0</ref> Test Automation is a development discipline as it uses scripting languages to instruct the tool how to interact with your application. As such careful consideration needs to be paid to

* Exception handling for bugs that occur during testing cycles(i.e, unexpected error messages during a test run).
* How the tool synchronizes with your application(e.g. if there are slow response times from your environment)
* The level of maintenance required to keep the tests up to date with changes in the application [http://en.wikipedia.org/wiki/Graphical_user_interface GUI](i.e, new buttons, data fields, custom controls etc)

Any test automation framework is a set of assumptions, concepts and tools that provide support for automating the major activities in the testing process. The main advantage of a framework is

* Increased Productivity
* Easy and Reduced maintenance effort
* Consistent automation development across projects
* Process driven than person driven approach
* Controlled maintenance of automation artifacts

There is a range of automation testing tools available. Some of them are licensed and few others are open sourced. QTP, Cucumber, Capybara and other tools<ref>http://en.wikipedia.org/wiki/List_of_web_testing_tools</ref>

=='''Description'''==
Although HP UFT is usually used for UI based Test Case Automation, it can also automate some non-UI based test cases like database testing, webservice testing and file based operations. It offers a graphical user interface, keyboard support, multiple testing views, and scripting language.
<ref>http://www.softwaretestinghelp.com/qtp-quicktest-professional-tutorial-1/</ref>
===Data Driven Testing===
HP Unified Functional Testing supports data-driven testing. For example, data can be output to a data table for reuse elsewhere. [http://en.wikipedia.org/wiki/Data-driven_testing Data-driven testing] is implemented as a Microsoft Excel workbook that can be accessed from HP Unified Functional Testing. HP Unified Functional Testing has two types of data tables: the Global data sheet and Action (local) data sheets. The test steps can read data from these data tables in order to drive variable data into the application under test, and verify the expected result.<ref>http://www.qtp10.com/2009/07/using-global-and-action-data-sheets-in.html</ref>

===Views===
HP Unified Functional Testing provides two views—and ways to modify—a test script: Keyword View and Expert View. These views enable HP Unified Functional Testing to act as an Integrated Development Environment (IDE) for the test, and HP Unified Functional Testing includes many standard IDE features, such as breakpoints to pause a test at predetermined places.<ref>http://en.wikipedia.org/wiki/HP_QuickTest_Professional</ref>

====Keyword view====
Keyword View lets users create and view the steps of a test in a modular, table format. In Keyword View, users can also view properties for items such as checkpoints, output values, and actions, use conditional and loop statements, and insert breakpoints to assist in debugging a test.<ref>http://www.qtp10.com/2009/07/working-with-keyword-view-in-hp-qtp.html</ref>

====Expert View====
Expert view displays test code using [http://en.wikipedia.org/wiki/VBScript VBScript]. Designed for more advanced users, users can edit all test actions except for the root Global action, and changes are synchronized with the Keyword View.<ref>http://www.fdscallcentre.com/homepage/data/mi/DS-0413-020_QTPro6.0.pdf</ref>

===Scripting===
HP UFT's VBScript allows for classes, but not other object oriented properties such as inheritance and polymorphism. It also lacks a debugger, however UFT has a debugger provided by HP. Some Windows script (WScript,WSH,WMI) & VB.Net code can be used in a script in the expert view <ref>https://h20546.www2.hp.com/main/training/course_details.cfm?Course=00008165&sitepick=US</ref>

===Exception handling===
Application crashes, Unexpected events and errors during a run session can disrupt the run session and distort results. This is a problem particularly when tests run unattended—the test pauses until one performs the operation needed to recover. To handle such situations, Error and Exception Handling is must while developing script or Automation Framework.<ref>http://qtpautomationcodes.blogspot.com/2013/05/error-handling-in-qtp.html</ref>
Error and Exception handling in HP UFT can be done by the following ways:

* Conditional Statement
* On Error statement
* Recovery Scenarios

=='''Life Cycle'''==
[File:LifeCycle.jpg‎]]

=='''Comparison to other tools'''==
Tools such as Cucumber and Capybara run tests from the perspective of the user. Cucumber converts user stories into tests and Capybara simulates a user or web browser. Unified Functional Testing is used by programmers to preform specific test cases they code themselves.<ref>''Engineering Long-Lasting Software: An Agile Approach Using SaaS and Cloud Computing'', Beta Edition 0.9.0 by Armando Fox and David Patterson, August 23, 2012, p136, </ref>

'''Capybara''' interacts with a website the way a human would (like visiting a url, clicking a link, typing text into a form and submitting it). It is used to emulate a user's flow through a website. Test cases in Capybara will look like this:<ref>http://stackoverflow.com/questions/15004918/cucumber-vs-capybara</ref>
<pre>
describe "the signup process", :type => :feature do
before :each do
User.make(:email => 'user@example.com', :password => 'caplin')
end
it "signs me in" do
visit '/sessions/new'
within("#session") do
fill_in 'Login', :with => 'user@example.com'
fill_in 'Password', :with => 'password'
end
click_link 'Sign in'
page.should have_content 'Success'
end
end</pre>

'''Cucumber''' writes human-readable tests that are mapped onto code. With it, you can rewrite the above example like this:<ref>http://stackoverflow.com/questions/15004918/cucumber-vs-capybara</ref>

<pre>
Scenario: Signup process
Given a user exists with email "user@example.com" and password "caplin"
When I try to login with "user@example.com" and "caplin"
Then I should be logged in successfully
</pre>

'''Selenium''' is a tool for automating web applications for testing purposes.

'''Comparison of UFT with other tools'''<ref>http://www.aspiresys.com/WhitePapers/QTPvsSelenium.pdf</ref>
{| border="1" class="wikitable"
|+
! Feature
! UFT
! Selenium
! Cucumber/ Capybara
|-
! Windows (Non-browser)
based Application support
| Yes
| No
| No
|-
! Environment Support
| Only Windows
| Windows , Linux , Solaris
OS X , Others
| Windows , Linux , Solaris
OS X , Others
|-
! Windows (Non-browser)
based Application support
| Yes
| No
| No
|-
!Software Cost
| License & Annual maintenance Fees
| Zero
| Zero
|-
!Coding Experience of
Engineer
|Not Much
|Should be very good along with
technical capabilities of integrating
different pieces of framework
|Requires minimal use of Ruby programming
|-
!Script Creation Time
|Low
|High
|Medium
|-
!Hardware resource (CPU
+ RAM) consumption during
script execution
|High
|Low
|Low
|-
!Product Support
|Dedicate HP support along with
support forums
|Open Source Community
|Open Source Community
|-
!Framework
|Easily integrated with HP Quality
Center or HP ALM
|Selenium + Eclipse + Maven / ANT
+ Jenkins / Hudson & its plugins /
Cruise Control + TestNG + SVN
|Ruby on Rails
Merb
Sinatra
|-
!Continuous Integration
|Possible through Quality Center
/ ALM or Jenkins
|Possible through Jenkins / Hudson
/ Cruise Control
|Possible through Rake, Ant, Maven and JUnit output
|}

=='''Disadvantages'''==
Unified Functional Testing is developed mainly for Windows based systems and it relies on outdated Windows tools like VBXScript. Tests can not be run outside of the UFT environment nor are they compatible with all browser types.<ref>http://www8.hp.com/us/en/software-solutions/unified-functional-testing-automated-testing/demos-documents.html#!&pd1=1</ref>

=='''References'''==
<references/>

File:LifeCycle.jpg

2014-09-16T01:31:20Z

Abora: uploaded a new version of "File:LifeCycle.jpg"

File:LifeCycle.jpg

2014-09-16T01:24:43Z

Abora:

CSC/ECE 517 Fall 2014/ch1a 22 as

2014-09-16T01:19:35Z

Abora:

'''HP Unified Functional Testing Professional'''

HP Unified Functional Testing (UFT) software, formerly known as HP Quick Test Professional (QTP),<ref>http://www.automationrepository.com/2012/12/hp-unified-functional-testing-uft-11-5-new-features</ref> provides functional testing and regression testing automation for software applications and environments.<ref>http://www8.hp.com/us/en/software-solutions/application-lifecycle-management-application-test-software/index.html?zn=bto&cp=1-11-127-24^1352_4000_1__</ref> HP Unified Functional Testing can be used for enterprise quality assurance.<ref>http://www.learnqtp.com/qtp-quality-center-test-director-guide/</ref> HP Unified Functional Testing is a test automation tool originally developed by Mercury Interactive and later acquired by [http://en.wikipedia.org/wiki/Hewlett-Packard].<ref> http://www.devbistro.com/articles/Testing/Mercury-QuickTest-Professional-Evaluation</ref> HP Unified Functional Testing 11.5 combined HP QuickTest Professional and HP Service Test into a single software package,<ref> http://selftechy.com/2013/10/07/hp-uft-11-50-unified-functional-testing</ref> which is currently available from the HP Software Division. The integrated HP Unified Functional Testing software allows developers to test from a single console all three layers of a program’s operations: the interface, the service layer and the database layer.<ref>http://www.computerworld.com/article/2493313/data-center/hp-simplifies-automated-software-testing-suite.html</ref>

[https://docs.google.com/document/d/1eq3XHiUUBIrEBx-R2Mgolaw7HttSgzPniwDLEF5oVk0/edit# Writeup page.]
{| align=right style="border: 1px solid gray;" class="wikitable"
|+ HP Unified Functional Testing<ref>http://en.wikipedia.org/wiki/HP_QuickTest_Professional</ref>
|-
| [http://en.wikipedia.org/wiki/Software_developer? Developer(s)] || [http://en.wikipedia.org/wiki/Hewlett-Packard? HP], [http://en.wikipedia.org/wiki/HP_Software_Division? HP Software Division]
|-
| [http://en.wikipedia.org/wiki/Software_release_life_cycle? Stable release] || 12.01
|-
| [http://en.wikipedia.org/wiki/Operating_system? Operating system] || [http://en.wikipedia.org/wiki/Microsoft_Windows? Microsoft Windows]
|-
| [http://en.wikipedia.org/wiki/List_of_software_categories? Type] || [http://en.wikipedia.org/wiki/Test_automation? Test automation tools]
|-
| [http://en.wikipedia.org/wiki/Software_license? License] || [http://en.wikipedia.org/wiki/Proprietary_software? Proprietary]
|}

=='''Background'''==
Test automation is the use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions.<ref>''The Testing Network, An Integral Approach to Test Activities in Large Software Projects'' by Jean-Jacques Pierre Henry (Aug 17, 2008), p413, ISBN 978-3-540-78504-0</ref> Test Automation is a development discipline as it uses scripting languages to instruct the tool how to interact with your application. As such careful consideration needs to be paid to

* Exception handling for bugs that occur during testing cycles(i.e, unexpected error messages during a test run).
* How the tool synchronizes with your application(e.g. if there are slow response times from your environment)
* The level of maintenance required to keep the tests up to date with changes in the application GUI(i.e, new buttons, data fields, custom controls etc)

Any test automation framework is a set of assumptions, concepts and tools that provide support for automating the major activities in the testing process. The main advantage of a framework is

* Increased Productivity
* Easy and Reduced maintenance effort
* Consistent automation development across projects
* Process driven than person driven approach
* Controlled maintenance of automation artifacts

There is a range of automation testing tools available. Some of them are licensed and few others are open sourced. QTP, Cucumber, Capybara and other tools<ref>http://en.wikipedia.org/wiki/List_of_web_testing_tools</ref>

=='''Description'''==
Although HP UFT is usually used for UI based Test Case Automation, it can also automate some non-UI based test cases like database testing, webservice testing and file based operations. It offers a graphical user interface, keyboard support, multiple testing views, and scripting language.
<ref>http://www.softwaretestinghelp.com/qtp-quicktest-professional-tutorial-1/</ref>
===Data Driven Testing===
HP Unified Functional Testing supports data-driven testing. For example, data can be output to a data table for reuse elsewhere. Data-driven testing is implemented as a Microsoft Excel workbook that can be accessed from HP Unified Functional Testing. HP Unified Functional Testing has two types of data tables: the Global data sheet and Action (local) data sheets. The test steps can read data from these data tables in order to drive variable data into the application under test, and verify the expected result.<ref>http://www.qtp10.com/2009/07/using-global-and-action-data-sheets-in.html</ref>

===Views===
HP Unified Functional Testing provides two views—and ways to modify—a test script: Keyword View and Expert View. These views enable HP Unified Functional Testing to act as an Integrated Development Environment (IDE) for the test, and HP Unified Functional Testing includes many standard IDE features, such as breakpoints to pause a test at predetermined places.<ref>http://en.wikipedia.org/wiki/HP_QuickTest_Professional</ref>

====Keyword view====
Keyword View lets users create and view the steps of a test in a modular, table format. In Keyword View, users can also view properties for items such as checkpoints, output values, and actions, use conditional and loop statements, and insert breakpoints to assist in debugging a test.<ref>http://www.qtp10.com/2009/07/working-with-keyword-view-in-hp-qtp.html</ref>

====Expert View====
Expert view displays test code using [http://en.wikipedia.org/wiki/VBScript VBScript]. Designed for more advanced users, users can edit all test actions except for the root Global action, and changes are synchronized with the Keyword View.<ref>http://www.fdscallcentre.com/homepage/data/mi/DS-0413-020_QTPro6.0.pdf</ref>

===Scripting===
HP UFT's VBScript allows for classes, but not other object oriented properties such as inheritance and polymorphism. It also lacks a debugger, however UFT has a debugger provided by HP. Some Windows script (WScript,WSH,WMI) & VB.Net code can be used in a script in the expert view <ref>https://h20546.www2.hp.com/main/training/course_details.cfm?Course=00008165&sitepick=US</ref>

===Exception handling===
Application crashes, Unexpected events and errors during a run session can disrupt the run session and distort results. This is a problem particularly when tests run unattended—the test pauses until one performs the operation needed to recover. To handle such situations, Error and Exception Handling is must while developing script or Automation Framework.<ref>http://qtpautomationcodes.blogspot.com/2013/05/error-handling-in-qtp.html</ref>
Error and Exception handling in HP UFT can be done by the following ways:

* Conditional Statement
* On Error statement
* Recovery Scenarios

=='''Life Cycle'''==

=='''Comparison to other tools'''==
Tools such as Cucumber and Capybara run tests from the perspective of the user. Cucumber converts user stories into tests and Capybara simulates a user or web browser. Unified Functional Testing is used by programmers to preform specific test cases they code themselves.<ref>''Engineering Long-Lasting Software: An Agile Approach Using SaaS and Cloud Computing'', Beta Edition 0.9.0 by Armando Fox and David Patterson, August 23, 2012, p136, </ref>

'''Capybara''' interacts with a website the way a human would (like visiting a url, clicking a link, typing text into a form and submitting it). It is used to emulate a user's flow through a website. Test cases in Capybara will look like this:<ref>http://stackoverflow.com/questions/15004918/cucumber-vs-capybara</ref>
<pre>
describe "the signup process", :type => :feature do
before :each do
User.make(:email => 'user@example.com', :password => 'caplin')
end
it "signs me in" do
visit '/sessions/new'
within("#session") do
fill_in 'Login', :with => 'user@example.com'
fill_in 'Password', :with => 'password'
end
click_link 'Sign in'
page.should have_content 'Success'
end
end</pre>

'''Cucumber''' writes human-readable tests that are mapped onto code. With it, you can rewrite the above example like this:<ref>http://stackoverflow.com/questions/15004918/cucumber-vs-capybara</ref>

<pre>
Scenario: Signup process
Given a user exists with email "user@example.com" and password "caplin"
When I try to login with "user@example.com" and "caplin"
Then I should be logged in successfully
</pre>

'''Selenium''' is a tool for automating web applications for testing purposes.

'''Comparison of UFT with other tools'''<ref>http://www.aspiresys.com/WhitePapers/QTPvsSelenium.pdf</ref>
{| border="1" class="wikitable"
|+
! Feature
! UFT
! Selenium
! Cucumber/ Capybara
|-
! Windows (Non-browser)
based Application support
| Yes
| No
| No
|-
! Environment Support
| Only Windows
| Windows , Linux , Solaris
OS X , Others
| Windows , Linux , Solaris
OS X , Others
|-
! Windows (Non-browser)
based Application support
| Yes
| No
| No
|-
!Software Cost
| License & Annual maintenance Fees
| Zero
| Zero
|-
!Coding Experience of
Engineer
|Not Much
|Should be very good along with
technical capabilities of integrating
different pieces of framework
|Requires minimal use of Ruby programming
|-
!Script Creation Time
|Low
|High
|Medium
|-
!Hardware resource (CPU
+ RAM) consumption during
script execution
|High
|Low
|Low
|-
!Product Support
|Dedicate HP support along with
support forums
|Open Source Community
|Open Source Community
|-
!Framework
|Easily integrated with HP Quality
Center or HP ALM
|Selenium + Eclipse + Maven / ANT
+ Jenkins / Hudson & its plugins /
Cruise Control + TestNG + SVN
|Ruby on Rails
Merb
Sinatra
|-
!Continuous Integration
|Possible through Quality Center
/ ALM or Jenkins
|Possible through Jenkins / Hudson
/ Cruise Control
|Possible through Rake, Ant, Maven and JUnit output
|}

=='''Disadvantages'''==
Unified Functional Testing is developed mainly for Windows based systems and it relies on outdated Windows tools like VBXScript. Tests can not be run outside of the UFT environment nor are they compatible with all browser types.<ref>http://www8.hp.com/us/en/software-solutions/unified-functional-testing-automated-testing/demos-documents.html#!&pd1=1</ref>

=='''References'''==
<references/>

CSC/ECE 517 Fall 2014/ch1a 22 as

2014-09-16T01:14:04Z

Abora:

'''HP Unified Functional Testing Professional'''

HP Unified Functional Testing (UFT) software, formerly known as HP Quick Test Professional (QTP),<ref>http://www.automationrepository.com/2012/12/hp-unified-functional-testing-uft-11-5-new-features</ref> provides functional testing and regression testing automation for software applications and environments.<ref>http://www8.hp.com/us/en/software-solutions/application-lifecycle-management-application-test-software/index.html?zn=bto&cp=1-11-127-24^1352_4000_1__</ref> HP Unified Functional Testing can be used for enterprise quality assurance.<ref>http://www.learnqtp.com/qtp-quality-center-test-director-guide/</ref> HP Unified Functional Testing is a test automation tool originally developed by Mercury Interactive and later acquired by [http://en.wikipedia.org/wiki/Hewlett-Packard].<ref> http://www.devbistro.com/articles/Testing/Mercury-QuickTest-Professional-Evaluation</ref> HP Unified Functional Testing 11.5 combined HP QuickTest Professional and HP Service Test into a single software package,<ref> http://selftechy.com/2013/10/07/hp-uft-11-50-unified-functional-testing</ref> which is currently available from the HP Software Division. The integrated HP Unified Functional Testing software allows developers to test from a single console all three layers of a program’s operations: the interface, the service layer and the database layer.<ref>http://www.computerworld.com/article/2493313/data-center/hp-simplifies-automated-software-testing-suite.html</ref>

[https://docs.google.com/document/d/1eq3XHiUUBIrEBx-R2Mgolaw7HttSgzPniwDLEF5oVk0/edit# Writeup page.]
{| align=right style="border: 1px solid gray;" class="wikitable"
|+ HP Unified Functional Testing<ref>http://en.wikipedia.org/wiki/HP_QuickTest_Professional</ref>
|-
| [http://en.wikipedia.org/wiki/Software_developer? Developer(s)] || [http://en.wikipedia.org/wiki/Hewlett-Packard? HP], [http://en.wikipedia.org/wiki/HP_Software_Division? HP Software Division]
|-
| [http://en.wikipedia.org/wiki/Software_release_life_cycle? Stable release] || 12.01
|-
| [http://en.wikipedia.org/wiki/Operating_system? Operating system] || [http://en.wikipedia.org/wiki/Microsoft_Windows? Microsoft Windows]
|-
| [http://en.wikipedia.org/wiki/List_of_software_categories? Type] || [http://en.wikipedia.org/wiki/Test_automation? Test automation tools]
|-
| [http://en.wikipedia.org/wiki/Software_license? License] || [http://en.wikipedia.org/wiki/Proprietary_software? Proprietary]
|}

=='''Background'''==
Test automation is the use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions.<ref>''The Testing Network, An Integral Approach to Test Activities in Large Software Projects'' by Jean-Jacques Pierre Henry (Aug 17, 2008), p413, ISBN 978-3-540-78504-0</ref> Test Automation is a development discipline as it uses scripting languages to instruct the tool how to interact with your application. As such careful consideration needs to be paid to

* Exception handling for bugs that occur during testing cycles(i.e, unexpected error messages during a test run).
* How the tool synchronizes with your application(e.g. if there are slow response times from your environment)
* The level of maintenance required to keep the tests up to date with changes in the application GUI(i.e, new buttons, data fields, custom controls etc)

Any test automation framework is a set of assumptions, concepts and tools that provide support for automating the major activities in the testing process. The main advantage of a framework is

* Increased Productivity
* Easy and Reduced maintenance effort
* Consistent automation development across projects
* Process driven than person driven approach
* Controlled maintenance of automation artifacts

There is a range of automation testing tools available. Some of them are licensed and few others are open sourced. QTP, Cucumber, Capybara and other tools<ref>http://en.wikipedia.org/wiki/List_of_web_testing_tools</ref>

=='''Description'''==
Although HP UFT is usually used for UI based Test Case Automation, it can also automate some non-UI based test cases like database testing, webservice testing and file based operations. It offers a graphical user interface, keyboard support, multiple testing views, and scripting language.
<ref>http://www.softwaretestinghelp.com/qtp-quicktest-professional-tutorial-1/</ref>
===Data Driven Testing===
HP Unified Functional Testing supports data-driven testing. For example, data can be output to a data table for reuse elsewhere. Data-driven testing is implemented as a Microsoft Excel workbook that can be accessed from HP Unified Functional Testing. HP Unified Functional Testing has two types of data tables: the Global data sheet and Action (local) data sheets. The test steps can read data from these data tables in order to drive variable data into the application under test, and verify the expected result.<ref>http://www.qtp10.com/2009/07/using-global-and-action-data-sheets-in.html</ref>

===Views===
HP Unified Functional Testing provides two views—and ways to modify—a test script: Keyword View and Expert View. These views enable HP Unified Functional Testing to act as an Integrated Development Environment (IDE) for the test, and HP Unified Functional Testing includes many standard IDE features, such as breakpoints to pause a test at predetermined places.<ref>http://en.wikipedia.org/wiki/HP_QuickTest_Professional</ref>

====Keyword view====
Keyword View lets users create and view the steps of a test in a modular, table format. In Keyword View, users can also view properties for items such as checkpoints, output values, and actions, use conditional and loop statements, and insert breakpoints to assist in debugging a test.<ref>http://www.qtp10.com/2009/07/working-with-keyword-view-in-hp-qtp.html</ref>

====Expert View====
Expert view displays test code using [http://en.wikipedia.org/wiki/VBScript VBScript]. Designed for more advanced users, users can edit all test actions except for the root Global action, and changes are synchronized with the Keyword View.<ref>http://www.fdscallcentre.com/homepage/data/mi/DS-0413-020_QTPro6.0.pdf</ref>

===Scripting===
HP UFT's VBScript allows for classes, but not other object oriented properties such as inheritance and polymorphism. It also lacks a debugger, however UFT has a debugger provided by HP. Some Windows script (WScript,WSH,WMI) & VB.Net code can be used in a script in the expert view <ref>https://h20546.www2.hp.com/main/training/course_details.cfm?Course=00008165&sitepick=US</ref>

===Exception handling===
Application crashes, Unexpected events and errors during a run session can disrupt the run session and distort results. This is a problem particularly when tests run unattended—the test pauses until one performs the operation needed to recover. To handle such situations, Error and Exception Handling is must while developing script or Automation Framework.<ref>http://qtpautomationcodes.blogspot.com/2013/05/error-handling-in-qtp.html</ref>
Error and Exception handling in HP UFT can be done by the following ways:

* Conditional Statement
* On Error statement
* Recovery Scenarios

=='''Life Cycle'''==

=='''Comparison to other tools'''==
Tools such as Cucumber and Capybara run tests from the perspective of the user. Cucumber converts user stories into tests and Capybara simulates a user or web browser. Unified Functional Testing is used by programmers to preform specific test cases they code themselves.<ref>''Engineering Long-Lasting Software: An Agile Approach Using SaaS and Cloud Computing'', Beta Edition 0.9.0 by Armando Fox and David Patterson, August 23, 2012, p136, </ref>

'''Capybara''' interacts with a website the way a human would (like visiting a url, clicking a link, typing text into a form and submitting it). It is used to emulate a user's flow through a website. Test cases in Capybara will look like this:<ref>http://stackoverflow.com/questions/15004918/cucumber-vs-capybara</ref>
<pre>
describe "the signup process", :type => :feature do
before :each do
User.make(:email => 'user@example.com', :password => 'caplin')
end
it "signs me in" do
visit '/sessions/new'
within("#session") do
fill_in 'Login', :with => 'user@example.com'
fill_in 'Password', :with => 'password'
end
click_link 'Sign in'
page.should have_content 'Success'
end
end</pre>

'''Cucumber''' writes human-readable tests that are mapped onto code. With it, you can rewrite the above example like this:<ref>http://stackoverflow.com/questions/15004918/cucumber-vs-capybara</ref>

<pre>
Scenario: Signup process
Given a user exists with email "user@example.com" and password "caplin"
When I try to login with "user@example.com" and "caplin"
Then I should be logged in successfully
</pre>

'''Selenium''' is a tool for automating web applications for testing purposes.

Comparison of QTP with other tools<ref>http://www.aspiresys.com/WhitePapers/QTPvsSelenium.pdf</ref>
{| border="1" class="wikitable"
|+
! Feature
! QTP
! Selenium
! Cucumber/ Capybara
|-
! Windows (Non-browser)
based Application support
| Yes
| No
| No
|-
! Environment Support
| Only Windows
| Windows , Linux , Solaris
OS X , Others
| Windows , Linux , Solaris
OS X , Others
|-
! Windows (Non-browser)
based Application support
| Yes
| No
| No
|-
!Software Cost
| License & Annual maintenance Fees
| Zero
| Zero
|-
!Coding Experience of
Engineer
|Not Much
|Should be very good along with
technical capabilities of integrating
different pieces of framework
|Requires minimal use of Ruby programming
|-
!Script Creation Time
|Low
|High
|Medium
|-
!Hardware resource (CPU
+ RAM) consumption during
script execution
|High
|Low
|Low
|-
!Product Support
|Dedicate HP support along with
support forums
|Open Source Community
|Open Source Community
|-
!Framework
|Easily integrated with HP Quality
Center or HP ALM
|Selenium + Eclipse + Maven / ANT
+ Jenkins / Hudson & its plugins /
Cruise Control + TestNG + SVN
|Ruby on Rails
Merb
Sinatra
|-
!Continuous Integration
|Possible through Quality Center
/ ALM or Jenkins
|Possible through Jenkins / Hudson
/ Cruise Control
|Possible through Rake, Ant, Maven and JUnit output
|}

=='''Disadvantages'''==
Unified Functional Testing is developed mainly for Windows based systems and it relies on outdated Windows tools like VBXScript. Tests can not be run outside of the UFT environment nor are they compatible with all browser types.<ref>http://www8.hp.com/us/en/software-solutions/unified-functional-testing-automated-testing/demos-documents.html#!&pd1=1</ref>

=='''References'''==
<references/>

CSC/ECE 517 Fall 2014/ch1a 22 as

2014-09-16T00:46:51Z

Abora:

'''HP Unified Functional Testing Professional'''

HP Unified Functional Testing (UFT) software, formerly known as HP Quick Test Professional (QTP),<ref>http://www.automationrepository.com/2012/12/hp-unified-functional-testing-uft-11-5-new-features</ref> provides functional and regression test automation for software applications and environments.<ref>http://www8.hp.com/us/en/software-solutions/application-lifecycle-management-application-test-software/index.html?zn=bto&cp=1-11-127-24^1352_4000_1__</ref> HP Unified Functional Testing can be used for enterprise quality assurance.<ref>http://www.learnqtp.com/qtp-quality-center-test-director-guide/</ref> HP Unified Functional Testing is a test automation tool originally developed by Mercury Interactive and later acquired by Hewlett Packard.<ref> http://www.devbistro.com/articles/Testing/Mercury-QuickTest-Professional-Evaluation</ref> HP Unified Functional Testing 11.5 combined HP QuickTest Professional and HP Service Test into a single software package,<ref> http://selftechy.com/2013/10/07/hp-uft-11-50-unified-functional-testing</ref> which is currently available from the HP Software Division. The integrated HP Unified Functional Testing software allows developers to test from a single console all three layers of a program’s operations: the interface, the service layer and the database layer.<ref>http://www.computerworld.com/article/2493313/data-center/hp-simplifies-automated-software-testing-suite.html</ref>

[https://docs.google.com/document/d/1eq3XHiUUBIrEBx-R2Mgolaw7HttSgzPniwDLEF5oVk0/edit# Writeup page.]
{| align=right style="border: 1px solid gray;" class="wikitable"
|+ HP Unified Functional Testing<ref>http://en.wikipedia.org/wiki/HP_QuickTest_Professional</ref>
|-
| [http://en.wikipedia.org/wiki/Software_developer? Developer(s)] || [http://en.wikipedia.org/wiki/Hewlett-Packard? HP], [http://en.wikipedia.org/wiki/HP_Software_Division? HP Software Division]
|-
| [http://en.wikipedia.org/wiki/Software_release_life_cycle? Stable release] || 12.01
|-
| [http://en.wikipedia.org/wiki/Operating_system? Operating system] || [http://en.wikipedia.org/wiki/Microsoft_Windows? Microsoft Windows]
|-
| [http://en.wikipedia.org/wiki/List_of_software_categories? Type] || [http://en.wikipedia.org/wiki/Test_automation? Test automation tools]
|-
| [http://en.wikipedia.org/wiki/Software_license? License] || [http://en.wikipedia.org/wiki/Proprietary_software? Proprietary]
|}

=='''Background'''==
Test automation is the use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions.<ref>The Testing Network: An Integral Approach to Test Activities in Large p413</ref> Test Automation is a development discipline as it uses scripting languages to instruct the tool how to interact with your application. As such careful consideration needs to be paid to

* Exception handling for bugs that occur during testing cycles(i.e, unexpected error messages during a test run).
* How the tool synchronizes with your application(e.g. if there are slow response times from your environment)
* The level of maintenance required to keep the tests up to date with changes in the application GUI(i.e, new buttons, data fields, custom controls etc)

Any test automation framework is a set of assumptions, concepts and tools that provide support for automating the major activities in the testing process. The main advantage of a framework is

* Increased Productivity
* Easy and Reduced maintenance effort
* Consistent automation development across projects
* Process driven than person driven approach
* Controlled maintenance of automation artifacts

There is a range of automation testing tools available. Some of them are licensed and few others are open sourced. QTP, Cucumber, Capybara and other tools<ref>http://en.wikipedia.org/wiki/List_of_web_testing_tools</ref>

=='''Description'''==
Although HP UFT is usually used for UI based Test Case Automation, it can also automate some non-UI based test cases like database testing, webservice testing and file based operations. It offers a graphical user interface, keyboard support, multiple testing views, and scripting language.
<ref>http://www.softwaretestinghelp.com/qtp-quicktest-professional-tutorial-1/</ref>
===Data Driven Testing===
HP Unified Functional Testing supports data-driven testing. For example, data can be output to a data table for reuse elsewhere. Data-driven testing is implemented as a Microsoft Excel workbook that can be accessed from HP Unified Functional Testing. HP Unified Functional Testing has two types of data tables: the Global data sheet and Action (local) data sheets. The test steps can read data from these data tables in order to drive variable data into the application under test, and verify the expected result.<ref>http://www.qtp10.com/2009/07/using-global-and-action-data-sheets-in.html</ref>

===Views===
HP Unified Functional Testing provides two views—and ways to modify—a test script: Keyword View and Expert View. These views enable HP Unified Functional Testing to act as an Integrated Development Environment (IDE) for the test, and HP Unified Functional Testing includes many standard IDE features, such as breakpoints to pause a test at predetermined places.<ref>http://en.wikipedia.org/wiki/HP_QuickTest_Professional</ref>

====Keyword view====
Keyword View lets users create and view the steps of a test in a modular, table format. In Keyword View, users can also view properties for items such as checkpoints, output values, and actions, use conditional and loop statements, and insert breakpoints to assist in debugging a test.<ref>http://www.qtp10.com/2009/07/working-with-keyword-view-in-hp-qtp.html</ref>

====Expert View====
Expert view displays test code using [http://en.wikipedia.org/wiki/VBScript VBScript]. Designed for more advanced users, users can edit all test actions except for the root Global action, and changes are synchronized with the Keyword View.<ref>http://www.fdscallcentre.com/homepage/data/mi/DS-0413-020_QTPro6.0.pdf</ref>

===Scripting===
HP UFT's VBScript allows for classes, but not other object oriented properties such as inheritance and polymorphism. It also lacks a debugger, however UFT has a debugger provided by HP. Some Windows script (WScript,WSH,WMI) & VB.Net code can be used in a script in the expert view <ref>https://h20546.www2.hp.com/main/training/course_details.cfm?Course=00008165&sitepick=US</ref>

===Exception handling===
Application crashes, Unexpected events and errors during a run session can disrupt the run session and distort results. This is a problem particularly when tests run unattended—the test pauses until one performs the operation needed to recover. To handle such situations, Error and Exception Handling is must while developing script or Automation Framework.<ref>http://qtpautomationcodes.blogspot.com/2013/05/error-handling-in-qtp.html</ref>
Error and Exception handling in HP UFT can be done by the following ways:

* Conditional Statement
* On Error statement
* Recovery Scenarios

=='''Life Cycle'''==

=='''Comparison to other tools'''==
Tools such as Cucumber and Capybara run tests from the perspective of the user. Cucumber converts user stories into tests and Capybara simulates a user or web browser. Unified Functional Testing is used by programmers to preform specific test cases they code themselves.<ref>Engineering Long Lasting Software p136</ref>

'''Capybara''' interacts with a website the way a human would (like visiting a url, clicking a link, typing text into a form and submitting it). It is used to emulate a user's flow through a website. Test cases in Capybara will look like this:<ref>http://stackoverflow.com/questions/15004918/cucumber-vs-capybara</ref>
<pre>
describe "the signup process", :type => :feature do
before :each do
User.make(:email => 'user@example.com', :password => 'caplin')
end
it "signs me in" do
visit '/sessions/new'
within("#session") do
fill_in 'Login', :with => 'user@example.com'
fill_in 'Password', :with => 'password'
end
click_link 'Sign in'
page.should have_content 'Success'
end
end</pre>

'''Cucumber''' writes human-readable tests that are mapped onto code. With it, you can rewrite the above example like this:<ref>http://stackoverflow.com/questions/15004918/cucumber-vs-capybara</ref>

<pre>
Scenario: Signup process
Given a user exists with email "user@example.com" and password "caplin"
When I try to login with "user@example.com" and "caplin"
Then I should be logged in successfully
</pre>

'''Selenium''' is a tool for automating web applications for testing purposes.

Comparison of QTP with other tools<ref>http://www.aspiresys.com/WhitePapers/QTPvsSelenium.pdf</ref>
{| border="1" class="wikitable"
|+
! Feature
! QTP
! Selenium
! Cucumber/ Capybara
|-
! Windows (Non-browser)
based Application support
| Yes
| No
| No
|-
! Environment Support
| Only Windows
| Windows , Linux , Solaris
OS X , Others
| Windows , Linux , Solaris
OS X , Others
|-
! Windows (Non-browser)
based Application support
| Yes
| No
| No
|-
!Software Cost
| License & Annual maintenance Fees
| Zero
| Zero
|-
!Coding Experience of
Engineer
|Not Much
|Should be very good along with
technical capabilities of integrating
different pieces of framework
|Requires minimal use of Ruby programming
|-
!Script Creation Time
|Low
|High
|Medium
|-
!Hardware resource (CPU
+ RAM) consumption during
script execution
|High
|Low
|Low
|-
!Product Support
|Dedicate HP support along with
support forums
|Open Source Community
|Open Source Community
|-
!Framework
|Easily integrated with HP Quality
Center or HP ALM
|Selenium + Eclipse + Maven / ANT
+ Jenkins / Hudson & its plugins /
Cruise Control + TestNG + SVN
|Ruby on Rails
Merb
Sinatra
|-
!Continuous Integration
|Possible through Quality Center
/ ALM or Jenkins
|Possible through Jenkins / Hudson
/ Cruise Control
|Possible through Rake, Ant, Maven and JUnit output
|}

=='''Disadvantages'''==
Unified Functional Testing is developed mainly for Windows based systems and it relies on outdated Windows tools like VBXScript. Tests can not be run outside of the UFT environment nor are they compatible with all browser types.<ref>http://www8.hp.com/us/en/software-solutions/unified-functional-testing-automated-testing/demos-documents.html#!&pd1=1</ref>

=='''References'''==
<references/>

CSC/ECE 517 Fall 2014/ch1a 22 as

2014-09-16T00:42:28Z

Abora:

'''HP Unified Functional Testing Professional'''

HP Unified Functional Testing (UFT) software, formerly known as HP Quick Test Professional (QTP),<ref>http://www.automationrepository.com/2012/12/hp-unified-functional-testing-uft-11-5-new-features</ref> provides functional and regression test automation for software applications and environments.<ref>http://www8.hp.com/us/en/software-solutions/application-lifecycle-management-application-test-software/index.html?zn=bto&cp=1-11-127-24^1352_4000_1__</ref> HP Unified Functional Testing can be used for enterprise quality assurance.<ref>http://www.learnqtp.com/qtp-quality-center-test-director-guide/</ref> HP Unified Functional Testing is a test automation tool originally developed by Mercury Interactive and later acquired by Hewlett Packard.<ref> http://www.devbistro.com/articles/Testing/Mercury-QuickTest-Professional-Evaluation</ref> HP Unified Functional Testing 11.5 combined HP QuickTest Professional and HP Service Test into a single software package,<ref> http://selftechy.com/2013/10/07/hp-uft-11-50-unified-functional-testing</ref> which is currently available from the HP Software Division. The integrated HP Unified Functional Testing software allows developers to test from a single console all three layers of a program’s operations: the interface, the service layer and the database layer.<ref>http://www.computerworld.com/article/2493313/data-center/hp-simplifies-automated-software-testing-suite.html</ref>

[https://docs.google.com/document/d/1eq3XHiUUBIrEBx-R2Mgolaw7HttSgzPniwDLEF5oVk0/edit# Writeup page.]
{| align=right style="border: 1px solid gray;" class="wikitable"
|+ HP Unified Functional Testing
|-
| [http://en.wikipedia.org/wiki/Software_developer? Developer(s)] || [http://en.wikipedia.org/wiki/Hewlett-Packard? HP], [http://en.wikipedia.org/wiki/HP_Software_Division? HP Software Division]
|-
| [http://en.wikipedia.org/wiki/Software_release_life_cycle? Stable release] || 12.01
|-
| [http://en.wikipedia.org/wiki/Operating_system? Operating system] || [http://en.wikipedia.org/wiki/Microsoft_Windows? Microsoft Windows]
|-
| [http://en.wikipedia.org/wiki/List_of_software_categories? Type] || [http://en.wikipedia.org/wiki/Test_automation? Test automation tools]
|-
| [http://en.wikipedia.org/wiki/Software_license? License] || [http://en.wikipedia.org/wiki/Proprietary_software? Proprietary]
|}

=='''Background'''==
Test automation is the use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions.<ref>The Testing Network: An Integral Approach to Test Activities in Large p413</ref> Test Automation is a development discipline as it uses scripting languages to instruct the tool how to interact with your application. As such careful consideration needs to be paid to

* Exception handling for bugs that occur during testing cycles(i.e, unexpected error messages during a test run).
* How the tool synchronizes with your application(e.g. if there are slow response times from your environment)
* The level of maintenance required to keep the tests up to date with changes in the application GUI(i.e, new buttons, data fields, custom controls etc)

Any test automation framework is a set of assumptions, concepts and tools that provide support for automating the major activities in the testing process. The main advantage of a framework is

* Increased Productivity
* Easy and Reduced maintenance effort
* Consistent automation development across projects
* Process driven than person driven approach
* Controlled maintenance of automation artifacts

There is a range of automation testing tools available. Some of them are licensed and few others are open sourced. QTP, Cucumber, Capybara and other tools<ref>http://en.wikipedia.org/wiki/List_of_web_testing_tools</ref>

=='''Description'''==
Although HP UFT is usually used for UI based Test Case Automation, it can also automate some non-UI based test cases like database testing, webservice testing and file based operations. It offers a graphical user interface, keyboard support, multiple testing views, and scripting language.
<ref>http://www.softwaretestinghelp.com/qtp-quicktest-professional-tutorial-1/</ref>
===Data Driven Testing===
HP Unified Functional Testing supports data-driven testing. For example, data can be output to a data table for reuse elsewhere. Data-driven testing is implemented as a Microsoft Excel workbook that can be accessed from HP Unified Functional Testing. HP Unified Functional Testing has two types of data tables: the Global data sheet and Action (local) data sheets. The test steps can read data from these data tables in order to drive variable data into the application under test, and verify the expected result.<ref>http://www.qtp10.com/2009/07/using-global-and-action-data-sheets-in.html</ref>

===Views===
HP Unified Functional Testing provides two views—and ways to modify—a test script: Keyword View and Expert View. These views enable HP Unified Functional Testing to act as an Integrated Development Environment (IDE) for the test, and HP Unified Functional Testing includes many standard IDE features, such as breakpoints to pause a test at predetermined places.<ref>http://en.wikipedia.org/wiki/HP_QuickTest_Professional</ref>

====Keyword view====
Keyword View lets users create and view the steps of a test in a modular, table format. In Keyword View, users can also view properties for items such as checkpoints, output values, and actions, use conditional and loop statements, and insert breakpoints to assist in debugging a test.<ref>http://www.qtp10.com/2009/07/working-with-keyword-view-in-hp-qtp.html</ref>

====Expert View====
Expert view displays test code using [http://en.wikipedia.org/wiki/VBScript VBScript]. Designed for more advanced users, users can edit all test actions except for the root Global action, and changes are synchronized with the Keyword View.<ref>http://www.fdscallcentre.com/homepage/data/mi/DS-0413-020_QTPro6.0.pdf</ref>

===Scripting===
HP UFT's VBScript allows for classes, but not other object oriented properties such as inheritance and polymorphism. It also lacks a debugger, however UFT has a debugger provided by HP. Some Windows script (WScript,WSH,WMI) & VB.Net code can be used in a script in the expert view <ref>https://h20546.www2.hp.com/main/training/course_details.cfm?Course=00008165&sitepick=US</ref>

===Exception handling===
Application crashes, Unexpected events and errors during a run session can disrupt the run session and distort results. This is a problem particularly when tests run unattended—the test pauses until one performs the operation needed to recover. To handle such situations, Error and Exception Handling is must while developing script or Automation Framework.<ref>http://qtpautomationcodes.blogspot.com/2013/05/error-handling-in-qtp.html</ref>
Error and Exception handling in HP UFT can be done by the following ways:

* Conditional Statement
* On Error statement
* Recovery Scenarios

=='''Life Cycle'''==

=='''Comparison to other tools'''==
Tools such as Cucumber and Capybara run tests from the perspective of the user. Cucumber converts user stories into tests and Capybara simulates a user or web browser. Unified Functional Testing is used by programmers to preform specific test cases they code themselves.<ref>Engineering Long Lasting Software p136</ref>

'''Capybara''' interacts with a website the way a human would (like visiting a url, clicking a link, typing text into a form and submitting it). It is used to emulate a user's flow through a website. Test cases in Capybara will look like this:<ref>http://stackoverflow.com/questions/15004918/cucumber-vs-capybara</ref>
<pre>
describe "the signup process", :type => :feature do
before :each do
User.make(:email => 'user@example.com', :password => 'caplin')
end
it "signs me in" do
visit '/sessions/new'
within("#session") do
fill_in 'Login', :with => 'user@example.com'
fill_in 'Password', :with => 'password'
end
click_link 'Sign in'
page.should have_content 'Success'
end
end</pre>

'''Cucumber''' writes human-readable tests that are mapped onto code. With it, you can rewrite the above example like this:<ref>http://stackoverflow.com/questions/15004918/cucumber-vs-capybara</ref>

<pre>
Scenario: Signup process
Given a user exists with email "user@example.com" and password "caplin"
When I try to login with "user@example.com" and "caplin"
Then I should be logged in successfully
</pre>

'''Selenium''' is a tool for automating web applications for testing purposes.

Comparison of QTP with other tools<ref>http://www.aspiresys.com/WhitePapers/QTPvsSelenium.pdf</ref>
{| border="1" class="wikitable"
|+
! Feature
! QTP
! Selenium
! Cucumber/ Capybara
|-
! Windows (Non-browser)
based Application support
| Yes
| No
| No
|-
! Environment Support
| Only Windows
| Windows , Linux , Solaris
OS X , Others
| Windows , Linux , Solaris
OS X , Others
|-
! Windows (Non-browser)
based Application support
| Yes
| No
| No
|-
!Software Cost
| License & Annual maintenance Fees
| Zero
| Zero
|-
!Coding Experience of
Engineer
|Not Much
|Should be very good along with
technical capabilities of integrating
different pieces of framework
|Requires minimal use of Ruby programming
|-
!Script Creation Time
|Low
|High
|Medium
|-
!Hardware resource (CPU
+ RAM) consumption during
script execution
|High
|Low
|Low
|-
!Product Support
|Dedicate HP support along with
support forums
|Open Source Community
|Open Source Community
|-
!Framework
|Easily integrated with HP Quality
Center or HP ALM
|Selenium + Eclipse + Maven / ANT
+ Jenkins / Hudson & its plugins /
Cruise Control + TestNG + SVN
|Ruby on Rails
Merb
Sinatra
|-
!Continuous Integration
|Possible through Quality Center
/ ALM or Jenkins
|Possible through Jenkins / Hudson
/ Cruise Control
|Possible through Rake, Ant, Maven and JUnit output
|}

=='''Disadvantages'''==
Unified Functional Testing is developed mainly for Windows based systems and it relies on outdated Windows tools like VBXScript. Tests can not be run outside of the UFT environment nor are they compatible with all browser types.<ref>http://www8.hp.com/us/en/software-solutions/unified-functional-testing-automated-testing/demos-documents.html#!&pd1=1</ref>

=='''References'''==
<references/>

CSC/ECE 517 Fall 2014/ch1a 22 as

2014-09-14T19:04:26Z

Abora:

'''HP Unified Functional Testing Professional'''

HP Unified Functional Testing (UFT) software, formerly known as HP Quick Test Professional (QTP),[1] provides functional and regression test automation for software applications and environments.[2] HP Unified Functional Testing can be used for enterprise quality assurance.[3] HP Unified Functional Testing is a test automation tool originally developed by Mercury Interactive and later acquired by Hewlett Packard.[1] HP Unified Functional Testing 11.5 combined HP QuickTest Professional and HP Service Test into a single software package,[7] which is currently available from the HP Software Division. The integrated HP Unified Functional Testing software allows developers to test from a single console all three layers of a program’s operations: the interface, the service layer and the database layer.[8]

[https://docs.google.com/a/ncsu.edu/document/d/1XzVu0zEuk7LP4smGZV9lRpSx5-wri6oClpUAmGYPN44/edit# Writeup page.]

=='''Background'''==
Test automation is the use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions. Test Automation is a development discipline as it uses scripting languages to instruct the tool how to interact with your application. As such careful consideration needs to be paid to

* Exception handling for bugs that occur during testing cycles(i.e, unexpected error messages during a test run).
* How the tool synchronizes with your application(e.g. if there are slow response times from your environment)
* The level of maintenance required to keep the tests up to date with changes in the application GUI(i.e, new buttons, data fields, custom controls etc)

Any test automation framework is a set of assumptions, concepts and tools that provide support for automating the major activities in the testing process. The main advantage of a framework is

* Increased Productivity
* Easy and Reduced maintenance effort
* Consistent automation development across projects
* Process driven than person driven approach
* Controlled maintenance of automation artifacts

There is a range of automation testing tools available. Some of them are licensed and few others are open sourced. QTP, Cucumber, Capybara and other tools[]

=='''Description'''==
Although HP UFT is usually used for UI based Test Case Automation, it can also automate some non-UI based test cases like database testing, webservice testing and file based operations. It offers a graphical user interface, keyboard support, multiple testing views, and scripting language.
<ref>http://www.softwaretestinghelp.com/qtp-quicktest-professional-tutorial-1/</ref>
===Data Driven Testing===
HP Unified Functional Testing supports data-driven testing. For example, data can be output to a data table for reuse elsewhere. Data-driven testing is implemented as a Microsoft Excel workbook that can be accessed from HP Unified Functional Testing. HP Unified Functional Testing has two types of data tables: the Global data sheet and Action (local) data sheets. The test steps can read data from these data tables in order to drive variable data into the application under test, and verify the expected result.[12]

===Views===
HP Unified Functional Testing provides two views—and ways to modify—a test script: Keyword View and Expert View. These views enable HP Unified Functional Testing to act as an Integrated Development Environment (IDE) for the test, and HP Unified Functional Testing includes many standard IDE features, such as breakpoints to pause a test at predetermined places.

====Keyword view====
Keyword View lets users create and view the steps of a test in a modular, table format. In Keyword View, users can also view properties for items such as checkpoints, output values, and actions, use conditional and loop statements, and insert breakpoints to assist in debugging a test.

====Expert View====
Expert view displays test code using [http://en.wikipedia.org/wiki/VBScript VBScript]. Designed for more advanced users, users can edit all test actions except for the root Global action, and changes are synchronized with the Keyword View.[17]

===Scripting===
HP UFT's VBScript allows for classes, but not other object oriented properties such as inheritance and polymorphism. It also lacks a debugger, however UFT has a debugger provided by HP. Some Windows script (WScript,WSH,WMI) & VB.Net code can be used in a script in the expert view <ref>https://h20546.www2.hp.com/main/training/course_details.cfm?Course=00008165&sitepick=US</ref>

===Exception handling===
Application crashes, Unexpected events and errors during a run session can disrupt the run session and distort results. This is a problem particularly when tests run unattended—the test pauses until one performs the operation needed to recover. To handle such situations, Error and Exception Handling is must while developing script or Automation Framework.
Error and Exception handling in HP UFT can be done by the following ways:

* Conditional Statement
* On Error statement
* Recovery Scenarios

=='''Life Cycle'''==

=='''Comparison to other tools'''==
Tools such as Cucumber and Capybara run tests from the perspective of the user. Cucumber converts user stories into tests and Capybara simulates a user or web browser. Unified Functional Testing is used by programmers to preform specific test cases they code themselves.<ref>Engineering Long Lasting Software p136</ref>

'''Capybara''' is a tool that interacts with a website the way a human would (like visiting a url, clicking a link, typing text into a

form and submitting it). It is used to emulate a user's flow through a website. With Capybara you can write something like this:
<pre>
describe "the signup process", :type => :feature do
before :each do
User.make(:email => 'user@example.com', :password => 'caplin')
end
it "signs me in" do
visit '/sessions/new'
within("#session") do
fill_in 'Login', :with => 'user@example.com'
fill_in 'Password', :with => 'password'
end
click_link 'Sign in'
page.should have_content 'Success'
end
end</pre>

'''Cucumber''' is a tool to write human-readable tests that are mapped into code. With it, you can rewrite the above example like this:<ref>http://stackoverflow.com/questions/15004918/cucumber-vs-capybara</ref>

<pre>
Scenario: Signup process
Given a user exists with email "user@example.com" and password "caplin"
When I try to login with "user@example.com" and "caplin"
Then I should be logged in successfully
</pre>

'''Selenium''' is a tool for automating web applications for testing purposes.

Comparison of QTP with other tools<ref>http://www.aspiresys.com/WhitePapers/QTPvsSelenium.pdf</ref>
{| border="1" class="wikitable"
|+
! Feature
! QTP
! Selenium
! Cucumber/ Capybara
|-
! Windows (Non-browser)
based Application support
| Yes
| No
| No
|-
! Environment Support
| Only Windows
| Windows , Linux , Solaris
OS X , Others
| Windows , Linux , Solaris
OS X , Others
|-
! Windows (Non-browser)
based Application support
| Yes
| No
| No
|-
!Software Cost
| License & Annual maintenance Fees
| Zero
| Zero
|-
!Coding Experience of
Engineer
|Not Much
|Should be very good along with
technical capabilities of integrating
different pieces of framework
|Requires minimal use of Ruby programming
|-
!Script Creation Time
|Low
|High
|Medium
|-
!Hardware resource (CPU
+ RAM) consumption during
script execution
|High
|Low
|Low
|-
!Product Support
|Dedicate HP support along with
support forums
|Open Source Community
|Open Source Community
|-
!Framework
|Easily integrated with HP Quality
Center or HP ALM
|Selenium + Eclipse + Maven / ANT
+ Jenkins / Hudson & its plugins /
Cruise Control + TestNG + SVN
|Ruby on Rails
Merb
Sinatra
|-
!Continuous Integration
|Possible through Quality Center
/ ALM or Jenkins
|Possible through Jenkins / Hudson
/ Cruise Control
|Possible through Rake, Ant, Maven and JUnit output
|}

=='''Disadvantages'''==
Unified Functional Testing is developed mainly for Windows based systems and it relies on outdated Windows tools like VBXScript. Tests can not be run outside of the UFT environment nor are they compatible with all browser types.<ref>http://www8.hp.com/us/en/software-solutions/unified-functional-testing-automated-testing/demos-documents.html#!&pd1=1</ref>

=='''References'''==
<references/>

CSC/ECE 517 Fall 2014/ch1a 22 as

2014-09-14T18:16:47Z

Abora:

'''HP Unified Functional Testing Professional'''

HP Unified Functional Testing (UFT) software, formerly known as HP Quick Test Professional (QTP),[1] provides functional and regression test automation for software applications and environments.[2] HP Unified Functional Testing can be used for enterprise quality assurance.[3] HP Unified Functional Testing is a test automation tool originally developed by Mercury Interactive and later acquired by Hewlett Packard.[1] HP Unified Functional Testing 11.5 combined HP QuickTest Professional and HP Service Test into a single software package,[7] which is currently available from the HP Software Division. The integrated HP Unified Functional Testing software allows developers to test from a single console all three layers of a program’s operations: the interface, the service layer and the database layer.[8]

[https://docs.google.com/a/ncsu.edu/document/d/1XzVu0zEuk7LP4smGZV9lRpSx5-wri6oClpUAmGYPN44/edit# Writeup page.]

=='''Background'''==
Test automation is the use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions. Test Automation is a development discipline as it uses scripting languages to instruct the tool how to interact with your application. As such careful consideration needs to be paid to

* Exception handling for bugs that occur during testing cycles(i.e, unexpected error messages during a test run).
* How the tool synchronizes with your application(e.g. if there are slow response times from your environment)
* The level of maintenance required to keep the tests up to date with changes in the application GUI(i.e, new buttons, data fields, custom controls etc)

Any test automation framework is a set of assumptions, concepts and tools that provide support for automating the major activities in the testing process. The main advantage of a framework is

* Increased Productivity
* Easy and Reduced maintenance effort
* Consistent automation development across projects
* Process driven than person driven approach
* Controlled maintenance of automation artifacts

There is a range of automation testing tools available. Some of them are licensed and few others are open sourced. QTP, Cucumber, Capybara and other tools[]

=='''Description'''==
Although HP UFT is usually used for UI based Test Case Automation, it can also automate some non-UI based test cases like database testing, webservice testing and file based operations. It offers a graphical user interface, keyboard support, multiple testing views, and scripting language.
<ref>http://www.softwaretestinghelp.com/qtp-quicktest-professional-tutorial-1/</ref>
===Data Driven Testing===
HP Unified Functional Testing supports data-driven testing. For example, data can be output to a data table for reuse elsewhere. Data-driven testing is implemented as a Microsoft Excel workbook that can be accessed from HP Unified Functional Testing. HP Unified Functional Testing has two types of data tables: the Global data sheet and Action (local) data sheets. The test steps can read data from these data tables in order to drive variable data into the application under test, and verify the expected result.[12]

===Views===
HP Unified Functional Testing provides two views—and ways to modify—a test script: Keyword View and Expert View. These views enable HP Unified Functional Testing to act as an Integrated Development Environment (IDE) for the test, and HP Unified Functional Testing includes many standard IDE features, such as breakpoints to pause a test at predetermined places.

====Keyword view====
Keyword View lets users create and view the steps of a test in a modular, table format. In Keyword View, users can also view properties for items such as checkpoints, output values, and actions, use conditional and loop statements, and insert breakpoints to assist in debugging a test.

====Expert View====
Expert view displays test code using [http://en.wikipedia.org/wiki/VBScript VBScript]. Designed for more advanced users, users can edit all test actions except for the root Global action, and changes are synchronized with the Keyword View.[17]

===Scripting===
HP UFT's VBScript allows for classes, but not other object oriented properties such as inheritance and polymorphism. It also lacks a debugger, however UFT has a debugger provided by HP. Some Windows script (WScript,WSH,WMI) & VB.Net code can be used in a script in the expert view <ref>https://h20546.www2.hp.com/main/training/course_details.cfm?Course=00008165&sitepick=US</ref>

===Exception handling===
Application crashes, Unexpected events and errors during a run session can disrupt the run session and distort results. This is a problem particularly when tests run unattended—the test pauses until one performs the operation needed to recover. To handle such situations, Error and Exception Handling is must while developing script or Automation Framework.
Error and Exception handling in HP UFT can be done by the following ways:

* Conditional Statement
* On Error statement
* Recovery Scenarios

=='''Life Cycle'''==

=='''Comparison to other tools'''==
Tools such as Cucumber and Capybara run tests from the perspective of the user. Cucumber converts user stories into tests and Capybara simulates a user or web browser. Unified Functional Testing is used by programmers to preform specific test cases they code themselves.<ref>Engineering Long Lasting Software p136</ref>

'''Capybara''' is a tool that interacts with a website the way a human would (like visiting a url, clicking a link, typing text into a

form and submitting it). It is used to emulate a user's flow through a website. With Capybara you can write something like this:
<pre>
describe "the signup process", :type => :feature do
before :each do
User.make(:email => 'user@example.com', :password => 'caplin')
end
it "signs me in" do
visit '/sessions/new'
within("#session") do
fill_in 'Login', :with => 'user@example.com'
fill_in 'Password', :with => 'password'
end
click_link 'Sign in'
page.should have_content 'Success'
end
end</pre>

'''Cucumber''' is a tool to write human-readable tests that are mapped into code. With it, you can rewrite the above example like this:

<pre>
Scenario: Signup process
Given a user exists with email "user@example.com" and password "caplin"
When I try to login with "user@example.com" and "caplin"
Then I should be logged in successfully
</pre>

'''Selenium''' is a tool for automating web applications for testing purposes.

{| border="1" class="wikitable"
|+ Comparison of QTP with other tools
! Feature
! QTP
! Selenium
! Cucumber/ Capybara
|-
! Windows (Non-browser)
based Application support
| Yes || No || No
|-
! Environment Support
| Only Windows
| Windows , Linux , Solaris
OS X , Others
| Windows , Linux , Solaris
OS X , Others
|}

=='''Disadvantages'''==
Unified Functional Testing is developed mainly for Windows based systems and it relies on outdated Windows tools like VBXScript. Tests can not be run outside of the UFT environment nor are they compatible with all browser types.<ref>http://www8.hp.com/us/en/software-solutions/unified-functional-testing-automated-testing/demos-documents.html#!&pd1=1</ref>

=='''References'''==
<references/>