Rehearsal of QTP in 1 Hr: Interview Questions 31 – 40
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. 31: Briefly explain the utility of Table and Database Checkpoints?
By adding table checkpoints to your tests or components, you can check:
a) That a specified value is displayed in a cell in a table on your application.
b) The contents of databases accessed by your application.
The results displayed for table and database checkpoints are similar. When you run your test or component, QTP compares the expected results of the checkpoint to the actual results of the run session. If the results do not match, the checkpoint fails.
You can check that a specified value is displayed in a cell in a table by adding a table checkpoint to your test or component. For ActiveX tables, you can also check the properties of the table object.
To add a table checkpoint, you use the Checkpoint Properties dialog box. Table checkpoints are supported for Web and ActiveX applications, as well as for a variety of external add-in environments.
You can use database checkpoints in your test or component to check databases accessed by your Web site or application and to detect defects. You define a query on your database, and then you create a database checkpoint that checks the results of the query.
Database checkpoints are supported for all environments supported by QTP, by default, as well as for a variety of external add-in environments.
There are two ways to define a database query:
a) Use Microsoft Query. You can install Microsoft Query from the custom installation of Microsoft Office.
b) Manually define an SQL statement.
The Checkpoint timeout option is available only when creating a table checkpoint. It is not available when creating a database checkpoint
<<<<<< =================== >>>>>>
Q. 32: How do you check Bitmaps?
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. QTP 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.
When you run the test or component, QTP compares the object or selected area of the object currently displayed on the Web page or application with the bitmap stored when the test or component was recorded. If there are differences, QTP captures a bitmap of the actual object and displays it with the expected bitmap in the details portion of the Test Results window. By comparing the two bitmaps (expected and actual), you can identify the nature of the discrepancy. For more information on test results of a checkpoint, see Viewing Checkpoint Results.
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).
The results of bitmap checkpoints may be affected by factors such as operating system, screen resolution, and color settings.
<<<<<< =================== >>>>>>
Q. 33: Briefly explain the utility of Text/Text Area Checkpoint?
In the Text/Text Area Checkpoint Properties dialog box, you can specify the text to be checked as well as which text is displayed before and after the checked text. These configuration options are particularly helpful when the text string you want to check appears several times or when it could change in a predictable way during run sessions.
In Windows-based environments, if there is more than one line of text selected, the Checkpoint Summary pane displays [complex value] instead of the selected text string. You can then click Configure to view and manipulate the actual selected text for the checkpoint.
QTP automatically displays the Checked Text in red and the text before and after the Checked Text in blue. For text area checkpoints, only the text string captured from the defined area is displayed (Text Before and Text After are not displayed). To designate parts of the captured string as Checked Text and other parts as Text Before and Text After, click the Configure button. The Configure Text Selection dialog box opens
Checking XML :
XML (Extensible Markup Language) is a meta-markup language for text documents that is endorsed as a standard by the W3C. XML makes the complex data structures portable between different computer environments/operating systems and programming languages, facilitating the sharing of data.
XML files contain text with simple tags that describe the data within an XML document. These tags describe the data content, but not the presentation of the data. Applications that display an XML document or file use either Cascading Style Sheets (CSS) or XSL Formatting Objects (XSL-FO) to present the data.
You can verify the data content of XML files by inserting XML checkpoints. A few common uses of XML checkpoints are described below:
An XML file can be a static data file that is accessed in order to retrieve commonly used data for which a quick response time is needed�for example, country names, zip codes, or area codes. Although this data can change over time, it is normally quite static. You can use an XML file checkpoint to validate that the data has not changed from one application release to another.
An XML file can consist of elements with attributes and values (character data). There is a parent and child relationship between the elements, and elements can have attributes associated with them. If any part of this structure (including data) changes, your application’s ability to process the XML file may be affected. Using an XML checkpoint, you can check the content of an element to make sure that its tags, attributes, and values have not changed.
XML files are often an intermediary that retrieves dynamically changing data from one system. The data is then accessed by another system using Document Type Definitions (DTD), enabling the accessing system to read and display the information in the file. You can use an XML checkpoint and parameterize the captured data values in order to check an XML document or file whose data changes in a predictable way.
XML documents and files often need a well-defined structure in order to be portable across platforms and development systems. One way to accomplish this is by developing an XML schema, which describes the structure of the XML elements and data types. You can use schema validation to check that each item of content in an XML file adheres to the schema description of the element in which the content is to be placed.
<<<<<< =================== >>>>>>
Q. 34: What are the Features & Benefits of QTP?
1) Key word driven testing
2) Suitable for both client server and web based application
3) VB script as the script language
4) Better error-handling mechanism
5) Excellent data driven testing features
6) Operates stand-alone, or integrated into HP Business Process Testing and HP Quality Center.
It introduces next-generation zero-configuration Keyword Driven testing technology in QTP allowing for fast test creation, easier maintenance, and more powerful data-driving capability.
It identifies objects with Unique Smart Object Recognition, even if they change from build to build, enabling reliable unattended script execution.
It collapses test documentation and test creation to a single step with Auto-documentation technology.
It enables thorough validation of applications through a full complement of checkpoints.
<<<<<< =================== >>>>>>
Q. 35: How to handle the exceptions using recovery scenario manager in QTP?
You can instruct QTP to recover unexpected events or errors that occurred in your testing environment during test run. Recovery scenario manager provides a wizard that guides you through the defining recovery scenario.
Recovery scenario has three steps
1) Triggered Events
2) Recovery steps
3) Post Recovery Test-Run
<<<<<< =================== >>>>>>
Q. 36: What information does the columns in the Keyword View provide for each step?
As you recorded your test, QTP generated steps in the Keyword View representing each operation you performed in the Web browser.
The columns in the Keyword View show different information for each step, as follows:
1) Item: Displays the item for the step (test object, utility object, function call, or statement) in a hierarchical icon-based tree.
2) Operation: The operation to be performed on the item, for example, Click or Select.
3) Value: The argument values for the selected operation, for example, the mouse button to use when clicking the image.
4) Assignment: The assignment of a value to or from a variable so you can use the value later in the test.
5) Comment: Any textual information you want to add regarding the step, for example, Return to page used in first step of the test.
6) Documentation: Auto-documentation of what the step does, in an easy-to-understand sentence, for example, Click the “findFlights” image.
<<<<<< =================== >>>>>>
Q. 37: Why do we use Regular Expressions?
We create a text checkpoint for searching a specific text string. We can use regular expressions to increase the flexibility and adaptability of your tests.
Regular expressions enable QTP to identify objects and text strings with varying values.
You can use regular expressions when defining the properties of an object, the methods of an argument, when parameterizing a step, and when creating checkpoints with varying values.
<<<<<< =================== >>>>>>
Q. 38: Explain QTP Testing process ?
The QTP testing process consists of 6 main phases:
1) 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.
2) Recording a session on your application: As you navigate through your application, QTP 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.
3) 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.
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.
4) Debugging your test: If changes were made to the script, you need to debug it to check that it operates smoothly and without interruption.
5) Running your test on a new version of your application: You run a test to check the behavior of your application. While running, QTP connects to your application and performs each step in your test.
6) Analyzing the test results: You examine the test results to pinpoint defects in your application.
7) Reporting defects: As you encounter failures in the application when analyzing test results, you will create defect reports in Defect Reporting Tool.
<<<<<< =================== >>>>>>
Q. 39: What is parameterizing of Tests?
When you test your application, you may want to check how it performs the same operations with multiple sets of data.
For example, 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.
<<<<<< =================== >>>>>>
Q. 40: What is test object model in QTP?
The test object model is a large set of object types or classes that QTP 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 QTP can record for it.
A test object is an object that QTP creates in the test or component to represent the actual object in your application. QTP 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.
When you perform an operation on your application while recording, QTP:
# Identifies the QTP 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 QTP test object method
QTP 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.
QTP displays your step in the Keyword View like this:
QTP displays your step in the Expert View like this:
Browser(“Mercury Interactive”).Page(“Mercury Interactive”).
WebButton(“Find”).
Continue to Next Set of QTP Rehearsal Questions 41 – 50
An expert on R&D, Online Training and Publishing. He is M.Tech. (Honours) and is a part of the STG team since inception.