HP Unified Functional Testing

This presentations tells about the Test Automation and basic concepts of HP Unified Functional Testing (formerly known as QTP)

Transcript

1. HP Unified Functional Testing FORMERLY KNOWN AS QUICKTEST PROFESSIONAL
2. Course Contents  Why Test Automation?  Introduction to UFT  How to record and playback?  Object Reference Model  Object Repository  Data Parameterization  Checkpoints  Actions  Output Values  Transactions  Debugging
3. Interesting facts  UFT formerly known as QuickTest Professional  Developed by Mercury Interactive, later acquired by HP in 2006  In 2004, Jason Huggins developed Selenium.  Rivalry to HP UFT  First version 5.5 in 2001  Latest version 11.53 in 2013  Language: VB Script
4. Why Test Automation?  Speed  Repeatability  Programming capabilities  Test Coverage  Reliability  Reusability  Save Time
5. Case Study “The automation offered by HP Unified Functional Testing has enabled us to achieve excellent testing reproducibility and cost efficiency - allowing the work of 18 manual testers to be performed by only six employees.” Erich Barmet, Head of Test Management at CSS Insurance http://h20195.www2.hp.com/V2/GetPDF.aspx%2F4AA4-3936EEW.pdf “As an insurance firm, we simply cannot afford bugs in our software. We have to ensure the accuracy of all our benefit and premium calculations - both in the interest of our customers and the continuing solvency of our business,”
6. What next? What to automate?  Regression Test Cases  Data driven  Stress/Load/Endurance  Higher accuracy  Value of pi  Mission critical applications What not to automate?  Usability  One time testing  ASAP testing  Adhoc
7. Introduction to UFT  UFT = QTP + ST (Service Test)  UFT = GUI + API Testing  Flagship tool – Functional, Regression, and Services  Supports different technologies and applications such as : Java, .NET, PHPO, Mainframe, Siebel, SAP, etc.  Implements Microsoft Object Model  Latest Version: 11.53 supports Windows 8, IE 10, Chrome 27, 28, 29 (Beta)  Easy to navigate and learn  Integration with ALM/QC and HP Business Process Testing (component-based testing)
8. Installations/License  Administrator privileges are required.  Two types of licenses:  Seat  Concurrent  Add-ins needs to be procured  At least 2 GB RAM is required  More Info at UFT Availability Matrix - http://support.openview.hp.com/selfsolve/document/KM00225580
9. UFT User Interface
10. Record and Playback  Testers can record and playback business actions  Three types of recording:  Normal  Analog – Record mouse movements and keyboard strokes  Low-Level – Record x,y coordinates
11. Record & Playback Demo
12. Test Results
13. Object Reference Model
14. Object Reference Model Web Image Web Links Web button Web Text box
15. Object Reference Model Win Image Win Text box Win button TEST OBJECTS
16. Object Repository - RECORDING OBJECT REPOSITORY Button TEST OBJECTS Image Links … and so on …
17. Object Repository - PLAYBACK OBJECT REPOSITORY Button Image Links … and so on … RUN-TIME OBJECTS
18. Object Repository and Object Spy Demo
19. Actions  Actions are units that divide your test into logical sections.  Helps to achieve reusability  Types of Actions  Internal  External  Reusable  Copied Action  You can split the action into two
20. Actions Demo
21. Checkpoints  A checkpoint verifies that expected information is displayed in your application while the test is running.  Types of Checkpoints:  Standard  Image  Table  Page  Text  Text Area  Bitmap  Database  Accessibility  File Content  XML
22. Checkpoints Demo
23. Output Values  Used when the output for one action served as an input for a called action.  Types of Output Values:  Standard  Text  Text Area  Database  XML
24. Output Values Demo
25. Data Parameterization  Parameterization allows us to use various values at run time.  Reduces time and effort.  Data drivers can be used to put in the same data for different input boxes.
26. Data Parameterization Username user12 34 !@#$12 34 Pass!@ 343___
27. Data Parameterization Demo
28. Transactions  Process in your application that you are interested in measuring.  Include transactions to the section of your script to measure the time that is taken by your application to run those specified steps.
29. Transactions Demo
30. Debugging  On Error Resume Next  On Error Go To 0 ##################################  Watch Expressions  Variables  Command ##################################
31. Debugging Demo
32. Questions
33. Visit www.QAInsights.com for more tutorials