To have an understanding of the basics of QTP, you can visit http://qtpgoodtutorials.blogspot.com
QTP (Quick Test Professional) is an excellent Record/Playback tool which enables us to create tests and business components by doing a live recording of all the operations being performed by us on our application.
Introduction to Tests in QTP:
A Test is a set of several steps organized into one or more actions, which can be used to verify the compliance of our application in line with our expectations. In QTP, Test comprises of three types of actions like
1) Non-reusable action.
2) Reusable action.
3) External action.
Testing in QTP follows following six simple steps:
Step – 1: Planning
Prior to building a test in QTP, it is essential to do necessary planning for preparation of a sound infrastructure required. Planning may include:
a) Making a decision on the functionality we wish to be tested.
b) Making a decision as to whether to conduct brief tests aimed to check some specific functions of the application or checking the complete application / site.
c) Making a decision as to how to organize the object repositories.
Step – 2: Creation of Tests or Components
In QTP, a test or a component can be created by either of the following:
Method –1: Recording a session on the Application or the Web site
While doing navigation across our application, each & every step followed by us is graphically displayed by QTP as a row in the “Keyword View”.
The “Documentation” column of the “Keyword View” displays an easy to understand & self-explanatory description of each & every step taken by us. Here the term “Step” is an activity, which creates some change in our application, like clicking a link or an image or submitting a data form etc. etc.
Method –2: Building an object repository
An object repository is built & these objects are used to manually add steps in the “Keyword View” or the “Expert View”. The Test or components can subsequently be modified by using special testing options or with programming statements.
Step – 3: Insertion of Checkpoints in the Tests or Components
A checkpoint is a verification point, which draws a comparison among a recent value for some specified property with respect to the expected value for that property. The idea of inserting checkpoints in tests or components is to enables us to identify as to whether the application is functioning properly or not.
Step – 4: Replacement of Fixed Values with Parameters
Fixed values are replaced with parameters thereby broadening the scope of our test.
The test or component can be parameterized in order to ascertain the performance of the application under different set of input data. When parameterization of test or component is done, QTP automatically replaces the fixed values with parameters. Every execution, which uses a particular set of parameterized data, is known as an “Iteration”.
“Output Values” can be used to extract the data from our test or component. An “Output Value” is a value retrieved during the run session and subsequently fed into the Data Table or saved as a variable or a parameter. Such Output Value can be used as an Input Data in the Test or Component.
QTP is a highly versatile functional testing tool having several great features to improve the testing process. We can include several programming statements to QTP process for achieving highly complex testing goals.
Step – 5: Execution of the Test
Once the Tests or components are created, they are executed to check the application.
During execution of the test or component, QTP integrates with the application and performs each & every operation in the test or component, checks all text strings, objects, or tables already specified.
In case parameterization of the test has been done with parameters defined in Data Table, QTP repeats all the specified actions for every set of data values already defined by us.
Run the tests or components with a view to debug it. We can control the run session to identify and eliminate the defects in them.
We can use the following commands to execute a test or component step by step.
Step Into,
Step Over,
Step Out
Breakpoints can also be defined to pause the test or component at some pre-defined point. We can view the value of all variables in the test or component every time it pauses at some predefined breakpoint in the Debug Viewer.
Step – 6: Analysis of Results
It is the concluding portion of the test after running the test or component.
Results are viewed in the Results window: We can view a summary of all the results as well as have a detailed report.
Reporting of Defects: HP Quality Center is a very good Bug Logging tool having excellent compatibility with QTP. All the detected defects can be logged in its database. QTP can be pre instructed to automatically report every failed step during the run alternatively reporting can be done manually as well.
Keywords: QTP, quicktest, HP, quality center, record/playback, expert view, keyword view, reusable actions
No comments:
Post a Comment