HP QTP - QuickTest Prof. 10.0 Question Bank - Part 3

Q. 101: What is the process of capturing visible portion of an object in QTP?
QTP captures the visible part of the specified object as a bitmap and inserts a checkpoint in the test. QTP does not capture any part of the screen which happens to be scrolled off the screen. We can check an area of an application as a bitmap. While creating a test, we specify the area you want to check by selecting an object. We can check an entire object or any area within an object.
<<<<<< =================== >>>>>>
Q. 102: What is the process of comparing selected area of object with Bitmap stored in the checkpoint?
When we run the test, QTP compares the object or selected area of the object in the application with the bitmap stored in the checkpoint.
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), we can identify the nature of the discrepancy.
<<<<<< =================== >>>>>>
Q. 103: How can we define a time interval for QTP to perform a checkpoint successfully?
For defining some time interval (say in seconds) during which QTP shopuld attempt to perform the checkpoint successfully, we need to specify the Checkpoint Timeout. QTP continues to perform the checkpoint until it passes or until the timeout occurs. If the checkpoint does not pass before the timeout occurs, the checkpoint fails.
For example, suppose it takes some time for an object to achieve an expected state. Increasing the checkpoint timeout value in this case can help ensure that the object has sufficient time to achieve that state, enabling the checkpoint to pass (if the data matches) before the maximum timeout is reached.
<<<<<< =================== >>>>>>
Q. 104: How can we check the object property values in our application?
We can check that a specified object in our application has the property values we expect, by adding a standard checkpoint step to our test while recording or editing the test. Standard checkpoints compare the expected values of object properties to the object’s current values during a run session.
We can use standard checkpoints to perform checks on images, tables, Web page properties, and other objects within our application.
<<<<<< =================== >>>>>>
Q. 105: How can we identify a checkpoint in QTP?
We identify a checkpoint by its name. By default, the checkpoint name is the same as the name of the test object on which the checkpoint was created. We can specify a different name for the checkpoint or accept the default name.
If we want to rename a checkpoint, make sure that the name is unique, and it does not begin or end with a space, and does not contain the special charactesr like " := @@
<<<<<< =================== >>>>>>
Q. 106: How can we Insert statement option when adding a checkpoint during the recording?
The Insert statement option is not available when adding a checkpoint during recording or when modifying an existing object checkpoint.
It is available only when adding a new checkpoint to an existing test while editing it.
<<<<<< =================== >>>>>>
Q. 107: How can we compare the image files in the Image Checkpoint?
We can compare the image files in the Image Checkpoint by using the Compare image content option in the Image Checkpoint Properties dialog box. It compares the expected image source file with the graphic of the actual image source file. If the expected and actual images are different, QTP displays them both in the Test Results. If the images are identical, only one graphic is displayed.
<<<<<< =================== >>>>>>
Q. 108: How can we check the contents of tables in our application in QTP?
We can check the contents of tables in our application by adding table checkpoints to the test. For example, we can check that a specified value is displayed in a particular cell. We can also check the properties of the table object. For example, we can check that a table has the expected number of rows and columns.
When we run the test, the table checkpoint compares the actual data to the expected data, as defined in the checkpoint. If the results match, the checkpoint passes.
<<<<<< =================== >>>>>>
Q. 109: How do we compare actual cell values with the expected cell values in Tables in QTP?.
By using the Settings tab we can compare actual cell values with the expected cell values in tables. By using Verification type option we can compare following types of cell contents.
1) String Content: It is the default setting. It treats the cell values as strings and checks for the exact text, while ignoring spaces. For example, 2 and 2.00 are not recognized as the same string.
2) Numeric Content: Evaluates the content of the cell according to numeric values. For example, 2 and 2.00 are recognized as the same number.
3) Numeric Range: Compares the content of the cell against a numeric range, where the minimum and maximum values are any real number that we specify.
<<<<<< =================== >>>>>>
Q. 110: How can we check the location of a cell to be checked in a Column of a table?
By the use of Identify columns option available in Cell Identification tab. This specifies the location of the column containing the cells with which we want to compare the expected data. This is done in two ways:
1) By position: This is the Default option. It locates cells according to the column position. A shift in the position of the columns within the table results in a mismatch.
2) By column name: It locates cells according to the column name. A shift in the position of the columns within the table does not result in a mismatch. This option gets enabled only when the table contains more than one column.
Q. 111: How can we check the location of a cell to be checked in a Row of a table?
By the use of Identify columns option available in Cell Identification tab. This specifies the location of the row containing the cells with which you want to compare the expected data. This is done in two ways:
1) By row number: This is the Default option. It locates cells according to the row position. A shift in the position of any of the rows within the table results in a mismatch.
2) By selected key columns: It locates the rows containing the cells to be checked by matching the value of the cell whose column was previously selected as a key column. A shift in the position of the row does not result in a mismatch. If more than one row is identified, QTP checks the first matching row. We can use more than one key column to uniquely identify any row.
<<<<<< =================== >>>>>>
Q. 112: How can we ensure that a text string appears in a specified area in QTP?
With the help of Text Area Checkpoint, we can ensure that a particular text string appears within a defined area in a Windows application, according to the specified criteria. It is supported for a variety of QTP add-in environments, like Standard Windows, Java, Visual Basic, and ActiveX etc.
<<<<<< =================== >>>>>>
Q. 113: How QTP retrieves Text while checking the text during the test?
QTP tries to retrieve the text directly from the object. If QTP cannot retrieve the text in this manner in some case where the text happens to be the part of a picture, it tries to retrieve the text using an OCR commonly known as optical character recognition mechanism.
<<<<<< =================== >>>>>>
Q. 114: How can we check the databases accessed by our application in QTP?
We can use database checkpoints to check the databases accessed by your application. For this, we define a query on the database. Then we create a database checkpoint for checking the results of the query. A database query can be defined in two ways like:
1) By Microsoft Query: We can install Microsoft Query from the custom installation of the Microsoft Office.
2) By manually defining an SQL statement.
<<<<<< =================== >>>>>>
Q. 115: How can we check a current data value with a value stored in a database in QTP?
With the help of database checkpoint we can check a current data value with a value stored in the database. When we run the test, the database checkpoint compares the current data in the database to the expected data defined in the Database Checkpoint Properties dialog box. If the expected data and the current results do not match, the database checkpoint fails.
<<<<<< =================== >>>>>>
Q. 116: What is the maximum number of rows, which can be defined in a database in QTP?
We can specify a maximum of 32,000 rows.
<<<<<< =================== >>>>>>
Q. 117: What is XML?
XML also called as Extensible Markup Language is a meta-markup language for text documents. This is recognized as a standard by the World Wide Web Consortium or called W3C in short. XML makes the complex data structures portable between different computer environments 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.
<<<<<< =================== >>>>>>
Q. 118: How can we verify the data content of XML files?
With the help of XML checkpoints, we can verify the data content of XML files. Common uses of XML checkpoints are:
1) We can validate that the data has not changed from one application release to the other.
2) We can check the content of an element to make sure that its tags, attributes, and values have not changed.
3) We can verify that the web service returns the XML in the expected structure and with the expected values.
<<<<<< =================== >>>>>>
Q. 119: What are the various types of XML checkpoints in QTP?
We can create three types of XML checkpoints in QTP:
1) XML Web Page / Frame Checkpoint: This checks an XML document within a Web page or frame.
2) XML File Checkpoint: This checks a specified XML file.
3) XML Test Object Checkpoint: This checks the XML data for an object or operation.
<<<<<< =================== >>>>>>
Q. 120: What is the use of XML Checkpoints on Web service operations?
XML Checkpoints on Web service operations compare the expected values of the checkpoint to the actual values returned from the last native Web service operation performed on the test object.
If a different Web service operation step is performed prior to the checkpoint, then the checkpoint will fail.
Q. 121: What is the use of XML Tree?
XML tree displays the hierarchical relationship between each element and value in the XML tree, enabling us to select the specific elements, attributes and values we want to check. Each element is displayed with a (X) icon. Each value is displayed with a (V) icon.
<<<<<< =================== >>>>>>
Q. 122: How many types of element checks are available in XML Checkpoints in QTP?
1) Check number of attributes: It checks the number of attributes that are attached to the element.
2) Check number of child element occurrences in block: Displays the number of child elements associated with the selected parent element. If we select this option, QTP verifies that the number of child elements in your XML tree corresponds to the number that appears in the Check number of child element occurrences in block field.
<<<<<< =================== >>>>>>
Q. 123: What is Schema Validation?
We can activate Schema Validation button to confirm that the XML in our application or file adheres to the structure defined in a specific XML schema or schemas. We can validate the structure of the XML we are checking using one or more external schema files or using schema embedded within our XML document.
<<<<<< =================== >>>>>>
Q. 124: What are the methods to populate the XML Tree?
We can use any one of the following three methods to populate the XML tree:
1) Updating the XML Tree Manually
2) Importing an XML Tree from a File
3) Updating the XML Tree Using Update Run Mode
<<<<<< =================== >>>>>>
Q. 125: What are the special guidelines for Schema Validation?
We consider following guidelines when specifying a schema file to validate our XML.
1) If we are validating an XML file using a schema defined in the XML file, the schema can be defined with an absolute or relative path. When we specify a relative path, QTP searches for the schema in the folders listed in the Folders tab of the Options dialog box.
2) If we are validating an XML document located on the Web with a schema file located on our file system, we cannot use UNC format (for example, \\ComputerName\Path\To\Schema) to specify the schema file location. Instead, map the schema file location to a network drive.
3) If there is a schema with a namespace defined in our XML document, the namespace of the external schema must be identical to the one defined in our document.
4) When we perform a schema validation, QTP validates all of the elements in the XML document, even if certain XML elements are not associated with a schema file. Any XML elements that are not associated with a schema file will cause the schema validation to fail.
<<<<<< =================== >>>>>>
Q. 126: What is the use of Parameterizing in QTP?
We can use the parameter feature in QTP to enhance our test by parameterizing the values that it uses. A parameter is a variable that is assigned a value from an external data source or generator.
We can parameterize values in steps and checkpoints in your test. We can also parameterize the values of action parameters.
<<<<<< =================== >>>>>>
Q. 127: What is the use of Data Driver when adding parameters in QTP?
If we want to parameterize the same value in several steps in our test, it is better to use the Data Driver rather than adding parameters manually.
<<<<<< =================== >>>>>>
Q. 128: How can we parameterize a step in QTP?
We can parameterize a step by using a test or action input parameter. This enables the step to use values that have been passed from the application that ran our test. For example, we can use an input test parameter as the value for a method argument.
<<<<<< =================== >>>>>>
Q. 129: What is the use of Data Table Parameters in QTP?
We can supply the list of possible values for a parameter by creating a Data Table parameter. Data Table parameters enable us to create a data-driven test, or action that runs several times using the data you supply. In each repetition, or iteration, QTP uses a different value from the Data Table.
We could conduct the test by accessing the Web site and recording the submission of numerous queries. This is a slow, laborious, and inefficient solution. By using Data Table parameters, we can run the test for multiple queries in succession.
<<<<<< =================== >>>>>>
Q. 130: What are the options available for configuring Data Table Parameters?
1) Name: Specifies the name of the parameter in the Data Table. We can create a new parameter by using the default parameter name or entering a new, descriptive name. Alternatively, we can select an existing Data Table parameter from the list.
2) Location in Data Table: Specifies whether to store the parameter in the global or current action sheet in the Data Table.
Q. 131: What is the use of Data Table formula in parametrization of data tables?
Data Table formula option inserts two columns in the Data Table. The first column contains a formula that checks the validity of output in the second column.
QTP uses the data in the output column to compute the formula, and inserts a value of TRUE or FALSE in the table cell of the formula column. This option is available only for the checkpoints.
<<<<<< =================== >>>>>>
Q. 132: What is the use of Global Data Table parameters in QTP?
Global Data Table parameters take data from the Global sheet in the Data Table. The Global sheet contains the data that replaces global parameters in each iteration of the test.
By default, the test runs one iteration for each row in the Global sheet of the Data Table. Using the Run tab of the Test Settings dialog box, we can also set the test to run only one iteration, or to run iterations on specified rows within the Global sheet of the Data Table. We can use the parameters defined in the Global data sheet in any action.
<<<<<< =================== >>>>>>
Q. 133: What is the use of Local Data Table parameters in QTP?
Local Data Table parameters take data from the action’s sheet in the Data Table. The data in the action’s sheet replaces the action’s Data Table parameters in each iteration of the action. By default, actions run only one iteration.
If we have multiple rows in a local data sheet, the corresponding action runs multiple times before running the next action in the test.
<<<<<< =================== >>>>>>
Q. 134: What is the use of Environment parameters in QTP?
Environment parameters are useful for localization testing, when we want to test an application where the user interface strings change, depending on the selected language. Environment parameters can be used for testing the same application on different browsers. We can also vary the input values for each language by selecting a different Data Table file each time we run the test.
<<<<<< =================== >>>>>>
Q. 135: What are the types of Environment Variables in QTP?
1) User-Defined Internal Variables: These are the variables that we define within the test. These variables are saved with the test and are accessible only within the test in which they were defined.
2) User-Defined External Variables: These are the variables that we predefine in the active external environment variables file. We can create as many files as we want and select an appropriate file for each test, or change files for each test run.
3) Built-in Variables: These are the variables that represent information about the test and the computer on which the test is run, such as Test path and Operating system. These variables are accessible from all tests, and are designated as read-only.
<<<<<< =================== >>>>>>
Q. 136: How do we use User-Defined External Environment Variables in QTP?
We can create a list of variable-value pairs in an external file in .xml format. We can then select the file as the active external environment variable file for a test and use the variables from the file as parameters.
We can set up your environment variable files manually, or we can define the variables in the Environment tab of the Test Settings dialog box and use the Export button to create the file with the correct structure.
<<<<<< =================== >>>>>>
Q. 137: Can we create many external variable files with same names & different values?
we can create several external variable files with the same variable names and different values and then run the test several times, using a different file each time. This is quite useful for localization testing.
<<<<<< =================== >>>>>>
Q. 138: How to use Environment Variable Files with Quality Center?
When working with Quality Center and environment variable files, we must save the environment variable file as an attachment in our Quality Center project before we specify the file in the Environment tab of the Test Settings dialog box.
We can add a new or an existing environment variable file to our Quality Center project. Note that adding an existing file from the file system to a Quality Center project creates a copy of the file in Quality Center. Thus, once we save the file to the project, changes made to the Quality Center environment variable file will not affect the file system file and vice versa.
<<<<<< =================== >>>>>>
Q. 139: Where do we use Built-in Environment Variables in QTP?
QTP provides a set of built-in variables that enable us to use current information about the test and the QTP computer running our test. These can include the test name, the test path, the operating system type and version, and the local host name.
For example, we may want to perform different checks in our test based on the operating system being used by the computer that is running the test. To do this, we could include the OSVersion built-in environment variable in an If statement.
<<<<<< =================== >>>>>>
Q. 140: What are the options available for configuring Environment Variable Parameters?
1) Name option: Specifies the name of the parameter. For an internal user-defined environment variable parameter, we can create a new parameter by using the default parameter name or entering a new, descriptive name. Alternatively, we can select an existing internal user-defined environment variable parameter from the list.
2) Value option: Specifies the value of the parameter. We can enter the value for a new user-defined internal parameter, or modify the value for an existing user-defined internal parameter. External and built-in environment variable parameter values cannot be modified in this dialog box.
3) Type option: Specifies the type of environment variable parameter which are read-only:
a) Internal User-Defined
b) External User-Defined
c) Built-in
4) Regular expression option: Sets the value of the parameter as a regular expression. This option is available only when parameterizing a checkpoint or object property text string value, and the selected environment variable parameter type is internal user-defined.
Q. 141: What are the various options for configuring Random Number Parameters?
1) Numeric range: This option specifies the range from which the random number is generated. By default, the random number range is between 0 and 100. We can modify the range by entering different values in the From and To boxes. The range must be between 0 and 2147483647 (inclusive).
2) Name: This option assigns a name to our parameter. Assigning a name to a random parameter enables us to use the same parameter several times in our test. We can select an existing named parameter or create a new named parameter by entering a new, descriptive name.
3) Generate new random number: This option defines the generation timing for a named random parameter. This box is enabled when we select the Name check box. We can select one of the following options:
a) For each action iteration: This option generates a new number at the end of each action iteration.
b) For each test iteration: This option generates a new number at the end of each global iteration.
c) Once per entire test run: This option generates a new number the first time the parameter is used. The same number is used for the parameter throughout the test run.
<<<<<< =================== >>>>>>
Q. 142: How do we use Random Number Parameters for Non-Numeric Values?
Random number parameters are not suitable for non-numeric values, such as text or hypertext links.
<<<<<< =================== >>>>>>
Q. 143: What is the use of Data Driver in parameterizing the tests?
Data Driver help us to quickly parameterize several property values for test objects, checkpoints, and method arguments containing the same constant value within a given action.
We can choose to replace all occurrences of a selected constant value with a parameter, in the same way that we can use a Find and Replace All operation instead of a step-by-step Find and Replace process. QTP can show us each occurrence of the constant so that we can decide whether or not to parameterize the value.
<<<<<< =================== >>>>>>
Q. 144: Can we use Data Driver to parameterize the VBScript functions?
We cannot use the Data Driver to parameterize the values of arguments for user-defined methods or VBScript functions.
<<<<<< =================== >>>>>>
Q. 145: What is the use of Step-by-step parameterization option in Data Driver wizard?
Step-by-step parameterization enables us to view the current values of each step containing the selected value. For each step, we can choose whether or not to parameterize the value and if so, which parameterization options we want to use.
<<<<<< =================== >>>>>>
Q. 146: What is the use of Parameterize All option in Data Driver wizard?
Parameterize all option enables us to parameterize all occurrences of the selected value throughout the action. We set our parameterization preferences one time and the same options are applied to all occurrences of the value.
<<<<<< =================== >>>>>>
Q. 147: What is an Output Value Step in QTP?
An output value step is a step in which one or more values are captured at a specific point in our test and stored for the duration of the run session. The values can later be used as input at a different point in the run session.
<<<<<< =================== >>>>>>
Q. 148: What is the purpose of creating Output Value Steps in QTP
When we create output value steps, we can determine where the values are stored during the run session and how they can be used. During the run session, QTP retrieves each value at the specified point and stores it in the specified location. When the value is needed later in the run session, QTP retrieves it from this location and uses it as required.
<<<<<< =================== >>>>>>
Q. 149: What are the various categories of output values in QTP?
we can create following categories of output values:
1) Standard output values
2) Text and text area output values
3) Table output values
4) Database output values
5) XML output values
<<<<<< =================== >>>>>>
Q. 150: What is the purpose of Standard Output Values in QTP?
we can use standard output values for following:
1) To output the property values of most objects. For example, in a Web-based application, the number of links on a Web page may vary based on the selections a user makes on a form on the previous page. We can create an output value in our test to store the number of links on the page.
2) To output the contents of table cells.
3) To output text strings by specifying the text property of the object as an output value.