Interview Questions on QTP Part-1

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

Explain QTP Testing process ?

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.

How Does Run time data (Parameterization) is handled in QTP?

A) You can then enter test data into the Data Table, an integrated spreadsheet with the full functionality of Excel, to manipulate data sets and create multiple test iterations, without programming, to expand test case coverage. Data can be typed in or imported from

databases, spreadsheets, or text files.

What is keyword view and Expert view in QTP?

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.

Explain about the Test Fusion Report of QTP ?

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.

To which environments does 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.

Explain the QTP Tool interface.

 

 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. For additional information, refer to the QuickTest Professional User's Guide.

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. For additional information, refer to the QuickTest Professional User's Guide.

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

How QTP recognizes Objects in AUT?

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.

What are the types of Object Repositorys in QTP?

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.

Explain the check points in QTP?

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

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

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

How does QTP identifes the object in the application

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

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?

QTP handles those situations using “Regular Expressions”.

What is Parameterizing Tests?

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.

What is test object model in QTP ?

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 onwhich methods are performed during the run session.When you perform an operation on your application while recording,

QuickTest:

➤ identifies the QuickTest test object class that represents the object on which

you performed the operation and creates the appropriate test object

➤ reads the current value of the object’s properties in your application and

stores the list of properties and values with the test object

➤ chooses a unique name for the object, generally using the value of one of its

prominent properties

➤ records the operation that you performed on the object using the

appropriate QuickTest test object method

For example, suppose you click on a Find button with the following HTML

source code:

<INPUT TYPE="submit" NAME="Find" VALUE="Find">

QuickTest identifies the object that you clicked as a WebButton test object.

It creates a WebButton object with the name Find, and records the following properties and values for the Find WebButton: It also records that you performed a Click method on the WebButton.

QuickTest displays your step in the Keyword View like this:

QuickTest displays your step in the Expert View like this:

Browser("Mercury Interactive").Page("Mercury Interactive").

WebButton("Find").Click

What is Object Spy in QTP?

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.

Supported Check-Points in QTP?

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

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.

Many ways we can parameterize data in QTP ? 

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.

How do u do batch testing in WR & is it possible to do in QTP, if so explain?

Batch Testing in WR is nothing but running the whole test set by selecting "Run Testset" from the "Execution Grid".The same is possible with QTP also. If our test cases are automated then  by selecting "Run Testset" all the test scripts can be executed. In this process the Scripts get executed one by one by keeping all the remaining scripts in "Waiting" mode.

if i give some thousand tests to execute in 2 days what do u do?           

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

what does it mean when a check point is in red color? what do u do?

A red color indicates  failure. Here we analyze the the cause for failure whether it is a Script Issue or Envronment Issue or a Application issue.

what do you call the window testdirector-testlab?

"Execution Grid". It is place from where we Run all Manual / Automated Scripts

How do u create new test sets in TD

 A Login to TD.

Click on "Test Lab" tab.

 Select the Desired folder under which we need to Create the Test Set. ( Test Sets can be grouped as per module.)

Click on "New Test Set or Ctrl+N" Icon to create a Test Set.

How do u do batch testing in WR & is it possible to do in QTP, if so explain?

You can use Test Batch Runner to run several tests in succession. The results for each test are stored   in their default location.

Using Test Batch Runner, you can set up a list of tests and save the list as an .mtb file, so that you can easily run the same batch of tests again, at another time. You can also choose to include or exclude a test in your batch list from running during a batch run

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

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

What does it mean when a check point is in red color? what do u do?

A red color indicates  failure. Here we analyze the the cause for failure whether it is a  Script Issue or Envronment Issue or a Application issue.

What do you call the window testdirector-testlab?

"Execution Grid". It is place from where we Run all Manual / Automated Scripts

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

Datatable.Import "...XLS file name..."

                        DataTable.ImportSheet(FileName, SheetSource, SheetDest)

                        DataTable.ImportSheet "C:\name.xls" ,1 ,"name"