Professional Documents
Culture Documents
What is QTP?
QuickTest is a graphical interface record-playback automation tool. It is able to work with any web, java or windows client
application. Quick Test enables you to test standard web objects and ActiveX controls. In addition to these environments,
QuickTest Professional also enables you to test Java applets and applications and multimedia objects on Applications as well
as standard Windows applications, Visual Basic 6 applications and .NET framework applications...
QTP is Mercury Interactive Functional Testing Tool. QTP stands for Quality Test Professional.
Features & Benefits of Quick Test Professional?
* Key word driven testing
* Suitable for both client server and web based application
* Vb script as the scriot language
* Better error handling mechanism
* Excellent data driven testing features
Differences between QTP & WinRunner?
* QTP is object bases Scripting (VBS) where Winrunner is TSL (C based) Scripting.
* QTP supports ".NET" application Automation not available in Winrunner
* QTP has "Active Screen" support which captures the application, not available in WR.
* QTP has "Data Table" to store script values , variables which WR does not have.
* Using a “point and click” capability you can easily interface with objects, their definitions and create checkpoints after
having recorded a script – without having to navigate back to that location in your application like you have to with
WinRunner. This greatly speeds up script development.
To which environments do QTP supports?
QuickTest Professional supports functional testing of all enterprise environments, including Windows, Web, .NET, Java/J2EE,
SAP, Siebel, Oracle, PeopleSoft, Visual Basic, ActiveX, mainframe terminal emulators, and Web services.
What’s the QTP testing process?
QTP testing process consists of seven steps-
1.Create your test plan
2.Recording
3. Enhancing your script
4. Debugging
5. Run
6. Analyze
7. Report Defects (more…).
Create your test plan: Prior to automating there should be a detailed description of the test including the exact steps to
follow, data to be input, and all items to be verified by the test. The verification information should include both data
validations and existence or state verifications of objects in the application.
Recording a session on your application: As you navigate through your application, QuickTest graphically displays each
step you perform in the form of a collapsible icon-based test tree. A step is any user action that causes or makes a change in
your site, such as clicking a link or image, or entering data in a form.
Enhancing your test: Inserting checkpoints into your test lets you search for a specific value of a page, object or text
string, which helps you identify whether or not your application is functioning correctly.
NOTE: Checkpoints can be added to a test as you record it or after the fact via the Active Screen. It is much easier
and faster to add the checkpoints during the recording process.
Broadening the scope of your test by replacing fixed values with parameters lets you check how your application
performs the same operations with multiple sets of data.
Checkpoint
Description Example of Use
Type
Standard
Checks values of an object's properties. Check that a radio button is selected.
Checkpoint
Image
Checks the property values of an image. Check that the image source file is correct.
Checkpoint
Table
Checks information in a table. Check that the value in a table cell is correct.
Checkpoint
Bitmap Checks an area of a Web page or Check that a Web page (or any portion of it) is displayed as
Checkpoint application after capturing it as a bitmap expected.
Accessibility Identifies areas of a Web site to check for Check if the images on a Web page include ALT properties,
Checkpoint Section 508 compliancy. required by the W3C Web Content Accessibility Guidelines.
If the action called by the RunAction statement includes an ExitAction statement, the RunAction statement can return the
value of the ExitAction's RetVal argument.
How to export QTP results to an ".xls" file?
By default it creates an "XML" file and displays the results
How the exception handling can be done using QTP?
It can be done Using the Recovery Scenario Manager which provides a wizard that gudies you through the process of
defining a recovery scenario. FYI.. The wizard could be accesed in QTP> Tools-> Recovery Scenario Manager
How to do the scripting. Is there any inbuilt functions in QTP as in QTP-S. What is the difference between
them? how to handle script issues?
IF Condition THEN
Reporter.reportevent "-------"
END IF
3rd answer
1# Scripting in QTP is about working in expert view.
2# Creating User defined Functions using VB Scripts.
3# Using Conditional loops.
4# Manipulating with Functions, Test objects and Utilities.
5# Creating Libraries, creating startup script, creating init script.
Automation Frameworks using QTP
Frame work is a set of defined rules for automating a testing process.
There are 4 types of frame works in QTP
1.Linear frame work- recording and play back.
2. Modular frame work- creating scripts as a user defined function and calling that for test cases.
3. Keyword driven frame work- make changes in the keyword view of QTP and it’ll create scripts in script view.
4. Hybrid frame work- combination of any of above (it depends on complexity of scenario).
1. Linear framework- this is normal process like recording or scripting the program and executing it. This is not reusable,
once executing this script.
2. Modular framework- this is different from liner frame work, here recording or scripting the program and those script
split into actions and make those actions as reusable actions. These reusable actions can use any where in the test.
3. Keyword driven automation framework- QTP supports to keyword driven automation framework.
It's an application independent Automation Framework, this Framework will have following components:
1) Data tables /Excel Sheets containing Keywords, Object Names and Object Values. This is the only component which is
application dependent. Keywords are the words that we used to represent the test case.
For example VerifyEditbox. This can be used to represent the test case: Verify whether the Edit box is accepting the entered
text.
2) Test Driver. This contains the scripts to drive the test. Usually it will contain the code for taking keywords one by one from
the data table and call respective subroutines for each keyword using the Switch case statement.
3) Common Function Library. This contains all the common functions that are needed to test any application.
4. Hybrid frame work- combination of any of above (it depends on complexity of scenario).