Thursday, March 20, 2008

FAQ - Automation - QTP (151 to 160)

151. What is Framework?

A framework is nothing but a folder structure. It contains all the components that are using in Automation Architecture. Here components mean Object Repository, Library, Logs, Test Data, Script, Result etc

152. What are Compiled modules?

In QTP the compiled modules are called library files.

153. What is Automation Framework?

Automation frame work is nothing but a set of rules defined for developing and organizing the test scripts or it is a process to develop the automation scripts and reduce maintenance. This framework completely depends on the application, types of testing and tools that you are using. It’s hard to provide generalized framework for all applications:

154. In how many ways we can parameterize our test?

We can parameterize our tests in 4 ways.

* Test or component parameter
* Data Table parameter
* Environmental variable parameter
* Random number parameter

155. What are types of Table?

Types of tables are

* run time data table
* design time data table

156. How to add a text checkpoint to your test to check whether ‘welcome’ is displayed in your welcome page.

1 Locate the page where you want to add a text checkpoint.

2 Create a text checkpoint.
In the Active Screen, under your page highlight the text welcome. Right-click the highlighted text and choose Insert Text Checkpoint. The Text Checkpoint Properties dialog box opens.
When Checked Text appears in the list box, the Constant field displays the text string you highlighted. This is the text QuickTest looks for when running the test.
Click OK to accept the default settings in this dialog box.
QuickTest adds the text checkpoint to your test. It is displayed in the Keyword View as a checkpoint operation on your welcome page

3 Save the test.

157. How to Run and Analyze a Test with Checkpoints?

1 Expand the test and review your test.
Choose View > Expand All or use the * shortcut key on your number keypad.

2 Start running your test.
Click Run or choose Test > Run. The Run dialog box opens. Ensure that New run results folder is selected. Accept the default results folder name. Click OK. When the test run is completed, the Test Results window opens.

3 View the test results.
When QuickTest finishes running the test, the Test Results window opens. The test result should be passed, indicating that all checkpoints passed. If one or more checkpoints had failed, the test result would be failed.

4 View the results of the page checkpoint.
In the Details pane, you can review the details of the page checkpoint, which lists the items checked.

5 View the results of the table checkpoint.
In the Details pane, you can review the details of the table checkpoint. You can also review the values of the table cells (cell values that were checked are displayed in black; cell values that were not checked are displayed in gray).

6 View the results of the standard checkpoint.
In the Details pane, you can review the details of the standard checkpoint, which lists the properties that were checked and their values. The checkpoint passed because the actual values of the checked properties match the expected values.

7 View the results of the text checkpoint.
In the Details pane, you can review the details of the text checkpoint. The checkpoint passed because the actual text matches the expected text.

8 Close the Test Results window. Choose File > Exit.

158. How to Defining a Data Table Parameter for QTP?

1 Start QuickTest and open the Checkpoint test.
2 Save the test as Parameter.
3 Confirm that the Active Screen option is enabled.
4 Confirm that the Data Table option is enabled.
5 Select the text to parameterize.
6 Set the parameterization properties.

159. How to add a runtime parameter to a datasheet?

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

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

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

No comments: