Rehearsal of QTP in 1 Hr: Interview Questions 41 – 50
While appearing in an interview for a position on HP QuickTest Professional, do a quick rehearsal of your knowledge on this tool.
Here is a collection of 180 short questions, QTP Managers commonly use while interviewing new aspirants for their organization.
The entire rehearsal of these questions can take less than an hour.
Set of Ten Questions
Q. 41: How to analyze the test results using QTP?
When QTP finishes running the test, the Test Results window opens.
Initially, the Test Results window contains two panes for displaying the key elements of your test run.
#
The left pane displays the results tree, an icon-based view of the steps that were performed while the test was running. The results tree is organized according to the Web pages visited during the test run and can be expanded (+) to view each step.
The steps performed during the test run are represented by icons in the tree. You can instruct QTP to run a test or action more than once using different sets of data in each run. Each test run is called iteration, and each iteration is numbered. (The test you ran had only one iteration.)
# The right pane displays the test results details. The iteration summary table indicates which iterations passed and which failed. The status summary table indicates the number of checkpoints or reports that passed, failed, and raised warnings during the test.
View the test results for a specific step.
In the results tree, expand (+) Test Recording Summary > Recording Iteration 1 (Row 1) > Action1 Summary > your application > your test name.
The Test Results window now contains three panes, displaying:
# The results tree, with one step highlighted
# The test results details of the highlighted step
# The Active Screen, showing a screen capture of the Web page on which the step was performed.
When you click a page in the results tree, QTP displays the corresponding page in the application view. When you click a step (an operation performed on an object) in the results tree, the corresponding object is highlighted in the application view. In this case, the Departing From text box is highlighted.
<<<<<< =================== >>>>>>
Q. 42: Briefly tell me about the checkpoints in QTP?
A checkpoint verifies that expected information is displayed in an application while the test is running. You can add eight types of checkpoints to your test for standard web objects using QTP.
1) A page checkpoint checks the characteristics of an application
2) A text checkpoint checks that a text string is displayed in the appropriate place on an application
3) An object checkpoint (Standard) checks the values of an object on an application
4) An image checkpoint checks the values of an image on an application
5) A table checkpoint checks information within a table on an application
6) An Accessibility checkpoint checks the web page for statutory compliance.
7) An XML checkpoint checks the contents of individual XML data files or XML documents that are part of your Web application.
8) A database checkpoint checks the contents of databases accessed by your web site
<<<<<< =================== >>>>>>
Q. 43: In how many ways we can add checkpoints to an application using QTP?
We can add checkpoints while recording the application or we can add after recording is completed using Active screen
To perform the second one The Active screen must be enabled while recording
<<<<<< =================== >>>>>>
Q. 44: Explain the Automation Object Model of QTP in brief?
Essentially all configuration and run functionality provided via the QTP interface is in some way represented in the QTP automation object model via objects, methods, and properties.
Although a one-on-one comparison cannot always be made, most dialog boxes in QTP have a corresponding automation object, most options in dialog boxes can be set and/or retrieved using the corresponding object property, and most menu commands and other operations have corresponding automation methods.
You can use the objects, methods, and properties exposed by the QTP automation object model, along with standard programming elements such as loops and conditional statements to design your program.
<<<<<< =================== >>>>>>
Q. 45: Briefly explain the QTP Environment.
QTP environment uses the graphical interface and ActiveScreen technologies – A testing process for creating test scripts, relating manual test requirements to automated verification features – Data driving to use several sets of data using one test script.
<<<<<< =================== >>>>>>
Q. 46: Explain the concept as to how QTP identifies object.
During recording QTP looks at the object and stores it as test object.
For each test object QTP learns a set of default properties called mandatory properties, and look at the rest of the objects to check whether this properties are enough to uniquely identify the object.
During test run, QTP searches for the run time objects that matches with the test object it learned while recording.
<<<<<< =================== >>>>>>
Q. 47: Explain the 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.
<<<<<< =================== >>>>>>
Q. 48: Can we script any test case with out having Object repository? Or Using Object Repository is a must?
No. You can script with out Object repository by knowing the Window Handlers, spying and recognizing the objects logical names and properties available.
<<<<<< =================== >>>>>>
Q. 49: How to execute a WinRunner Script in QTP?
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:WinRunnerTestsbasic_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
<<<<<< =================== >>>>>>
Q. 50: Why should we divide a test into three action calls?
When you create a new test, it contains a call to one action.
By dividing your tests into calls to multiple actions, you can design more modular and efficient tests.
Continue to Next Set of QTP Rehearsal Questions 51 – 60
An expert on R&D, Online Training and Publishing. He is M.Tech. (Honours) and is a part of the STG team since inception.