QTP FAQS

1) What is QTP ?

A) 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...

2) Explain QTP Testing process ?

A) The QuickTest testing process consists of 6 main phases:

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.
Adding logic and conditional statements to your test enables you to add sophisticated checks to your test.

Debugging your test
If changes were made to the script, you need to debug it to check that it operates smoothly and without interruption.

Running your test on a new version of your application
You run a test to check the behavior of your application. While running, QuickTest connects to your application and performs each step in your test.

Analyzing the test results
You examine the test results to pinpoint defects in your application.

Reporting defects
As you encounter failures in the application when analyzing test results, you will create defect reports in Defect Reporting Tool.

3) Explain the QTP Tool interface.

A)It contains the following key elements:

Title bar, displaying the name of the currently open test
Menu bar, displaying menus of QuickTest commands
File toolbar, containing buttons to assist you in managing tests
Test toolbar, containing buttons used while creating and maintaining tests
Debug toolbar, containing buttons used while debugging tests.

Note: The Debug toolbar is not displayed when you open QuickTest for the first time. You can display the Debug toolbar by choosing View > Toolbars > Debug. Note that this tutorial does not describe how to debug a test.

Action toolbar, containing buttons and a list of actions, enabling you to view the details of an individual action or the entire test flow.

Note: The Action toolbar is not displayed when you open QuickTest for the first time. You can display the Action toolbar by choosing View > Toolbars > Action. If you insert a reusable or external action in a test, the Action toolbar is displayed automatically.

Test pane, containing two tabs to view your test-the Tree View and the Expert View
Test Details pane, containing the Active Screen

Data Table, containing two tabs, Global and Action, to assist you in parameterizing your test

Debug Viewer pane, containing three tabs to assist you in debugging your test-Watch Expressions, Variables, and Command. (The Debug Viewer pane can be opened only when a test run pauses at a breakpoint.)

Status bar, displaying the status of the test.

4) What is keyword view and Expert view in QTP?

A) QuickTest’s Keyword Driven approach, test automation experts
have full access to the underlying test and object properties, via an
integrated scripting and debugging environment that is round-trip
synchronized with the Keyword View.
Advanced testers can view and edit their tests in the Expert View,
which reveals the underlying industry-standard VBScript that
QuickTest Professional automatically generates. Any changes
made in the Expert View are automatically synchronized with the
Keyword View.

5) Explain about the Test Fusion Report of QTP ?

A) Once a tester has run a test, a TestFusion 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 pass and failure. By combining TestFusion reports with
QuickTest Professional, you can share reports across an entire QA
and development team.

6) To which environments does QTP supports ?

A) 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.

7) How QTP recognizes Objects in AUT?

A) QuickTest stores the definitions for application objects in a file called the Object Repository. As you record your test, QuickTest will add an entry for each item you interact with. Each Object Repository entry will be identified by a logical name (determined automatically by QuickTest), and will contain a set of properties (type, name, etc) that uniquely identify each object.
Each line in the QuickTest script will contain a reference to the object that you interacted with, a call to the appropriate method (set, click, check) and any parameters for that method (such as the value for a call to the set method). The references to objects in the script will all be identified by the logical name, rather than any physical, descriptive properties.

8) What are the types of Object Repositorys in QTP?

A) QuickTest has two types of object repositories for storing object information: shared object repositories and action object repositories. You can choose which type of object repository you want to use as the default type for new tests, and you can change the default as necessary for each new test.

The object repository per-action mode is the default setting. In this mode, QuickTest automatically creates an object repository file for each action in your test so that you can create and run tests without creating, choosing, or modifying object repository files. However, if you do modify values in an action object repository, your changes do not have any effect on other actions. Therefore, if the same test object exists in more than one action and you modify an object's property values in one action, you may need to make the same change in every action (and any test) containing the object.

9) Explain the check points in QTP?

A)A checkpoint verifies that expected information is displayed in a Application while the test is running. You can add eight types of checkpoints to your test for standard web objects using QTP.

A page checkpoint checks the characteristics of a Application
A text checkpoint checks that a text string is displayed in the appropriate place on a Application.
An object checkpoint (Standard) checks the values of an object on a Application.
An image checkpoint checks the values of an image on a Application.
A table checkpoint checks information within a table on a Application
An Accessiblity checkpoint checks the web page for Section 508 compliance.
An XML checkpoint checks the contents of individual XML data files or XML documents that are part of your Web application.
A database checkpoint checks the contents of databases accessed by your web site

10) In how many ways we can add check points to an application using QTP.

A) We can add checkpoints while recording the application or we can add after recording is completed using Active screen (Note : To perform the second one The Active screen must be enabled while recording).

11) How does QTP identifes the object in the application.

A) QTP identifies the object in the application by LogicalName and Class.
For example :
The Edit box is identified by
Logical Name : PSOPTIONS_BSE_TIME20
Class: WebEdit

12) If an application name is changes frequently i.e while recording it has name “Window1” and then while running its “Windows2” in this case how does QTP handles?

A)QTP handles those situations using “Regular Expressions”.

13) What is Parameterizing Tests?

A) When you test your application, you may want to check how it performs the same operations with multiple sets of data. For example, suppose you want to check how your application responds to ten separate sets of data. You could record ten separate tests, each with its own set of data. Alternatively, you can create a parameterized test that runs ten times: each time the test runs, it uses a different set of data.


14) What is test object model in QTP ?

A) The test object model is a large set of object types or classes that QuickTest
uses to represent the objects in your application. Each test object class has a
list of properties that can uniquely identify objects of that class and a set of
relevant methods that QuickTest can record for it.
A test object is an object that QuickTest creates in the test or component to
represent the actual object in your application. QuickTest stores information
about the object that will help it identify and check the object during the
run session.
A run-time object is the actual object in your Web site or application on
which methods are performed during the run session.

15) What is Object Spy in QTP?

A)Using the Object Spy, you can view the properties of any object in an open
application. You use the Object Spy pointer to point to an object. The Object
Spy displays the selected object’s hierarchy tree and its properties and values
in the Properties tab of the Object Spy dialog box.

16) What is the Diff between Image check-point and Bit map Check point?

A) Image checkpoints enable you to check the properties of a Web image.
You can check an area of a Web page or application as a bitmap. While
creating a test or component, you specify the area you want to check by
selecting an object. You can check an entire object or any area within an
object. QuickTest captures the specified object as a bitmap, and inserts a
checkpoint in the test or component. You can also choose to save only the
selected area of the object with your test or component in order to save disk Space
For example, suppose you have a Web site that can display a map of a city
the user specifies. The map has control keys for zooming. You can record the
new map that is displayed after one click on the control key that zooms in
the map. Using the bitmap checkpoint, you can check that the map zooms
in correctly.
You can create bitmap checkpoints for all supported testing environments
(as long as the appropriate add-ins are loaded).
Note: The results of bitmap checkpoints may be affected by factors such as
operating system, screen resolution, and color settings.

17) How many ways we can parameterize data in QTP ?

A) There are four types of parameters:
Test, action or component parameters enable you to use values passed
from your test or component, or values from other actions in your test.

Data Table parameters enable you to create a data-driven test (or action)
that runs several times using the data you supply. In each repetition, or
iteration, QuickTest uses a different value from the Data Table.

Environment variable parameters enable you to use variable values from
other sources during the run session. These may be values you supply, or
values that QuickTest generates for you based on conditions and options
you choose.

Random number parameters enable you to insert random numbers as
values in your test or component. For example, to check how your
application handles small and large ticket orders, you can have QuickTest
generate a random number and insert it in a number of tickets edit field.

18.If i give some thousand tests to execute in 2 days what do u do?

Ans : Adhoc testing is done. It Covers the least basic functionalities to verify that the system is working fine.

19. How to Import data from a ".xls" file to Data table during Runtime.

Ans : Datatable.Import "...XLS file name..."

DataTable.ImportSheet(FileName, SheetSource, SheetDest)
DataTable.ImportSheet "C:\name.xls" ,1 ,"name"


20.How to export data present in Datatable to an ".xls" file?

Ans : DataTable.Export "....xls file name..."

21. 3 differences between QTP & Winrunner?

Ans :
(a) QTP is object bases Scripting ( VBS) where Winrunner is TSL (C based) Scripting.
(b) QTP supports ".NET" application Automation not available in Winrunner
(c) QTP has "Active Screen" support which captures the application, not available in WR.
(d) QTP has "Data Table" to store script values , variables which WR does not have.
(e) 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.

22. how to add a runtime parameter to a datasheet?

Ans:
DataTable.LocalSheet

The following example uses the LocalSheet property to return the local sheet of
the run-time Data Table in order to add a parameter (column) to it.

MyParam=DataTable.LocalSheet.AddParameter("Time", "5:45")

23 .Object Repositories types, Which & when to use?

Deciding Which Object Repository Mode to Choose
To choose the default object repository mode and the appropriate object repository mode for each test, you need to understand the differences between the two modes.

In general, the object repository per-action mode is easiest to use when you are creating simple record and run tests, especially under the following conditions:

You have only one, or very few, tests that correspond to a given application, interface, or set of objects.
You do not expect to frequently modify test object properties.
You generally create single-action tests.
Conversely, the shared object repository mode is generally the preferred mode when:

You have several tests that test elements of the same application, interface, or set of objects.
You expect the object properties in your application to change from time to time and/or you regularly need to update or modify test object properties.
You often work with multi-action tests and regularly use the Insert Copy of Action and Insert Call to Action options.


24.How to execute a WinRunner Script in QTP?

Ans : (a) TSLTest.RunTest TestPath, TestSet [, Parameters ] --> Used in QTP , used for backward compatibility

Parameters : The test set within Quality Center, in which test runs are stored. Note that this argument is relevant only when working with a test in a Quality Center project. When the test is not saved in Quality Center, this parameter is ignored.

e.g : TSLTest.RunTest "D:\test1", ""


(b)
TSLTest.RunTestEx TestPath, RunMinimized, CloseApp [, Parameters ]

TSLTest.RunTestEx "C:\WinRunner\Tests\basic_flight", TRUE, FALSE, "MyValue"

CloseApp : Indicates whether to close the WinRunner application when the WinRunner test run ends.
Parameters : Up to 15 WinRunner function argument

25. How to handle Run-time errors?

(a) On Error Resume Next : causes execution to continue with the statement immediately following the statement that caused the run-time error, or with the statement immediately following the most recent call out of the procedure containing the On Error Resume Next statement. This allows execution to continue despite a run-time error. You can then build the error-handling routine inline within the procedure.
Using "Err" object msgbox "Error no: " & " " & Err.Number & " " & Err.description & " " & Err.Source & Err.HelpContext

26.How to change the run-time value of a property for an object?

Ans : SetTOProperty changes the property values used to identify an object during the test run.
Only properties that are included in the test object description can be set

27. How to retrieve the property of an object?

Ans : using "GetRoProperty".

28. How to open any application during Scripting?

Ans : SystemUtil , object used to open and close applications and processes during a run session.

(a) A SystemUtil.Run statement is automatically added to your test when you run an application from the Start menu or the Run dialog box while recording a test

E.g : SystemUtil.Run "Notepad.exe"
SystemUtil.CloseDescendentProcesses ( Closes all the processes opened by QTP )

29. Types of properties that Quick Test learns while recording?

Ans : (a) Mandatory (b) Assistive .

In addition to recording the mandatory and assistive properties specified in the Object Identification dialog box, QuickTest can also record a backup ordinal identifier for each test object. The ordinal identifier assigns the object a numerical value that indicates its order relative to other objects with an otherwise identical description (objects that have the same values for all properties specified in the mandatory and assistive property lists). This ordered value enables QuickTest to create a unique description when the mandatory and assistive properties are not sufficient to do so.

30. What is the extension of script and object repository files?

Ans : Object Repository : .tsr , Script : .mts, Excel : Default.xls

31. How to supress warnings from the "Test results page"?

Ans : From the Test results Viewer "Tools > Filters > Warnings"...must be "Unchecked".

32. How to covert a String to an integer?

Ans : CInt()---> a conversion function available.

33.Which keyword used for Normal Recording?

Ans:F3

34.Which keyword used for run the test script?

Ans:F5

35.Which keyword used for stop the recording?

Ans:F4

check this blog regularly for more testing faqs and articles.

Manual Faqs
Testing Material
Load Runner Faqs
Sql Server Faqs
Testing Faqs Resources
Descriptive Programming for Yahoo Login Page