Automation Tool QTP
Download as PPTX, PDF0 likes243 views
Quick Test Professional (QTP) is an automated functional testing tool by Hewlett Packard that utilizes Visual Basic Scripting for application automation. It features a graphical record-playback interface, supports both web and Windows applications, and enables testers to create, manage, and execute test plans with functionalities such as object repositories, output values, and library functions. QTP provides various types of actions, environment variables, and reporting mechanisms, significantly improving testing efficiency and accuracy while reducing cycle time.
Automation Tool QTP
- 1. Automation Tool - QTP
- 2. QTP stands for Quick Test Professional, a product of Hewlett Packard (HP). This tool helps testers to perform an automated functional testing seamlessly without monitoring once script development is complete. HP QTP uses Visual Basic Scripting (VBScript) for automating the applications ..Quick Test is a graphical interface record-playback automation-testing tool. It is able to work with any web or windows application.
- 3. QTP Testing Process Creating test plan Recording a session on application Enhancing the test by inserting checkpoints, parameterization statements, or inserting logical statements in the test Running a session of the test Analyzing the test results from test fusion report Reporting defects if any by connecting with quality center.
- 4. Object Repository When we record a test, QuickTest adds each object on which we perform operations to a file called local object repository so it can identify objects during run-time. We can also add objects to the local object repository while editing our test. Test objects can be stored in two types of object repositories—a shared object repository and a local object repository.
- 5. Types of Object Repository There are two types of object repository: Shared Object Repository Local Object Repository A shared object repository stores test objects in a file that can be accessed by multiple tests. A local object repository stores test objects in a file that is associated with one specific action, so that only that action can access the stored objects.
- 6. Managing Shared Object Repository Shared Object Repository can be created two ways: After creating the recording go to Object Repository window from Resource > Object Repository. Then File > Export Local Objects. Save the file at specific location with .tsr extension We can Manage Shared Object Repository also from Resource > Object Repository Manager
- 7. Shared Repository can be Accessible to any Test from Resource > Associate Repositories or From Keyword view – Right Click the Action Name, Click Action Properties > Associated Repositories If user wants some change in Shared Object Repository then user can go to Object Repository > Right click on the component to change > Click on “Copy to Local” and can modify the component. This modified Object Repository will be saved with test but will not affect the Original Shared Object Repository. If User wants this change to already saved Shared Object Repository, then User can do it from Object Repository Manager by Opening the Shared Object Repository then Enable Editing from File > Enable Editing. Then Tools > Update From Local Repository.
- 8. How QTP Identify Objects? QuickTest uses some properties for every test object to identify that object during run time. Properties values of test object are captured from object while recording. QuickTest uses the values of these properties to identify objects in the application during a run session. These are mandatory properties. If mandatory properties are not enough to uniquely identify an object, QuickTest adds some assistive properties. If several assistive properties are defined for an object class, then QuickTest learns one assistive property at a time and stops as soon as it creates a unique description for the object.
- 9. If QTP is unsuccessful to identify an object uniquely with both mandatory and assistive properties it use smart identification mechanism (Base Filter Properties & Optional Filter Properties). If both the learned description and smart identification fails, QTP uses ordinal identifier (Index, Location, and Creation Time properties). In order to configure the mandatory, assistive, and ordinal identifier properties and to enable and configure the Smart Identification mechanism, you can use Object Identification dialog box (Tools > Object Identification).
- 10. How QTP Identify Objects?
- 11. Output Value Output values enable to capture the values that the application generates during run time. When parameterized, the values change for each iteration. Thus by creating output values; we can capture the values for each run and output and store them to the data table. These values can be used later in the different point in application.
- 12. Output values are stored in run time data table; it is located in QTP result window and can be retrieved later. Types of Output Values: 1. Standard output value 2.Text output value 3. Database output value 4. XML output value
- 13. Output Value Types 1) Standard output value: We can use standard output values to output the properties values of most objects. We can use Standard Output value under Recording mode from Insert menu >output value> standard output value. 2) Text output value: We can use Text output values to output text strings displayed in an application. When creating a text output value we can output a part of the objects text and we can also specify text before and after options.
- 14. We can use Standard Output value under Recording mode from Insert menu >output value> text output value. 3) Database output value: We can use Database output values to output the values stored in database table. We can use Standard Output value from Insert menu >output value> database output value. 4) XML output value: We can use XML output values to output the values of XML elements in XML documents. We can use Standard Output value under Recording mode from Insert menu >output value> xml output value.
- 15. Actions Actions break up the test into logical sections/units such as specific activities that we perform in our application.
- 16. Types of Actions There are two types of actions: Reusable actions Non-reusable actions Reusable action Can be used in other tests Can be used in same test, multiple times Non-reusable action Cannot be used in other tests Can be called in the same test, only once.
- 17. Global Sheet and Local Sheet Global Datasheet Unique for the entire test Sheet is named “Global” Any action can access and write data into Global Datasheet Global Sheet: All Actions in the test are iterated Local Datasheet Equal to number of actions Sheet is named “Action Name” of “Local Sheet” An action can read and write data into its own local datasheet only Local Sheet: Only corresponding action in test is iterated
- 18. Library Functions If we have repeatable steps in a test or in an action then we can use user-defined functions. User defined functions will make our test look shorter, easier to maintain. Time and resources can also be saved by implementing and using these user-defined reusable functions. User defined functions can be stored in a function library or within an action in the test. If the function is stored in a function library then we have to associate that function library to the test so that the test can call all the functions listed in that library. We can associate the function library to the test from File Settings Resources Tab.
- 19. Functions in an associated function library can be accessible: From Step Generator, From Operation column in keyword view, or by manually entering the function name in the expert view. We can create new function library by selecting File >> New >> Function Library. Functions in library file can be created manually or by using Function Definition Generators. We can save this file at a specified location with .qlf (by default) or .vbs or .txt extension
- 20. There are two types of functions:: Private Functions and Public Functions Private Functions: These can be accessed from within the function library itself and cannot be accessed from outside this function library. Public Functions: These can be accessed from any function library.
- 21. Object Spy Using the Object Spy, we can view the properties of test object and their values in an open application. There are two ways to use object spy in QTP We can select Object Spy option from Tool Menu in QTP We can select Object Spy option from Object repository Window by selecting Tools Object Spy
- 22. Environment Variables A variable declared and initialized in one action using Dim statement can’t be used in other actions or Test. So, by using environment variables we can use the variables in different actions. There are two types of environment variables: 1. User-defined (internal, & external) Note: we can’t change the value of external environment variables. 2. Built-in Note: we can’t change value of these variables. To set the value of a user-defined environment variable: Environment.value (“VariableName”) = NewValue
- 23. Analog & Low-Level Recording Low-level recording: It is used in case qtp is unable to recognize some objects and its properties. It is based on mouse clicks and the x, y co-ordinates that is instead of taking that object, will take the x, y co-ordinates of that object. Analog recording: This mode records every moment of mouse as we drag the mouse around the screen or application window. Useful for recording operations that cannot be recorded at the level of an object. E.g., A signature produced by dragging the mouse will be recorded in analog.
- 24. Analog recording and low-level recording require more disk space than normal recording mode. By-default recording mode is normal recording. We can switch to either Analog Recording or Low Level Recording in the middle of a recording session for specific steps. After we record the necessary steps using analog recording or low-level recording, we can return to normal recording mode for the remainder of our recording session.
- 25. Difference between Wait & Synchronization Point? Wait: In wait point, though the job is completed less than the specified time, it will wait for the specified time to be elapsed and then only we will have the result summary or move to the next job. Synchronization: once the job has been completed, we immediately gets the result sheet or we move to the next iteration. It won’t wait for the specified time to be elapsed.
- 26. What’s the Transaction We can measure how long it takes to run a section of our test by defining transactions. Transaction modes are: Start transaction, End transaction We can also use MercuryTimers() function also like: MercuryTimers("Timer1").Start MercuryTimers("Timer1").Stop() And also we can fetch the time taken to load a particular step in a variable like: Dim a a=MercuryTimers("Timer1")
- 27. Invoke the web application We can invoke the web/window application with use of systemutil.run("WebPath”) command in the Expert View e.g. systemutil.Run "iexplore.exe", www.ning.com
- 28. Test Fusion Report Once the tester run the test, a Test-Fusion report displays all aspects of the test run: a high-level results overview, an expandable Tree View of the test specifying exactly where application failures occurred, the test data used, application screen shots for every step that highlight any discrepancies, and detailed explanations of each checkpoint weather pass or failure. By combining Test-Fusion reports with Quality center, we can share reports across an entire QA and development team.
- 29. Benefits 1. Test automation enables one to achieve detailed product testing with significant reduction in test cycle time. 2.The efficiency of automated testing incorporated into product lifecycle can generate sustainable time and money savings. 3. Reliability 4. Consistency 5. Accuracy 6. re-usability 7. Better, faster testing 8. The up-most advantage of automation testing is that we need not have to do the testing on the same modules again & again. We can plan, record, enhance the script, & run the test script as and when desired.