Professional Documents
Culture Documents
Professional 8.0
(Basic)
Mercury QuickTest Professional
• Introduction to QTP
− QuickTest Professional, the Mercury advanced keyword-
driven testing solution enables you to test standard
Windows applications, Web objects, ActiveX controls, and
Visual Basic applications. You can also acquire additional
QuickTest add-ins for a number of special environments
(such as Java, Oracle, SAP Solutions, .NET Windows and
Web Forms, Siebel, PeopleSoft, Web services, and
terminal emulator applications).
QuickTest Window
The QuickTest window contains the following key elements:
A best practice when setting general options for QuickTest are to:
•Deselect all check boxes except “Save data for integrating with
performance testing …” and “Display Add-in Manager on
startup”.
•Click on “Restore Layout” button to reset screens to the initial
QuickTest Professional Options-
>Run
A best practice, when setting run options for QuickTest are to:
•Enable the normal mode. this ensures that the execution arrow
appears to help with trouble shooting your test.
•You can choose to have the test results appear after each test
run or not.
•Select "Allow other Mercury products to run tests and
components"
Record and Run Settings -
Windows
•
• Define Synchronization.
• Examine when and where synchronization is most helpful.
• Add a synchronization step for a specified object.
What is Synchronization ?
Using Checkpoints
• A recorded test is not considering valid without verification. Some
reasons for this may be to:
• Confirm that the test’s action procedure intended results.
• These results should adhere to company business rules.
Visual Cues
• What happens when the value of the object you are checking
changes from the original recorded Value (i.e., Agent Name)?
• The test checkpoint must be modified to accommodate changing
values.
• You can tell that a checkpoint has been added to a test when you
view the Test Result. A check mark appears next to the step. You
A Variable Checkpoint Value
• View the Test Results window to verify that each of the rows from
the Design Time Data Table was used during the test run.
• Expand the tree for each iteration (Row#) to view specific
information about the execution of the specific row.
The Run-Time Table
• Set the number of rows that will be driven into the test for the
specified field in the Run
• Setting dialog box.
• The possibilities are:
• - Run one iteration
• - Run all rows
• - Run a range of rows
Output Parameter
• In the Keyword View, choose a step that contains the field whose
value will be output.
• In the Active Screen, right-click on the field whose value you
want to output.
• Choose Insert Output Value from the list.
• Verify the object you want to output by clicking OK in the Object
Output Value Properties
• A different list of choices will appear when the variable type Built-
In is chosen.
7. Reusable and Multiple
Actions
Objectives
• List the types of actions that can be created.
• Discuss the benefits of reusable actions.
• Call a reusable action from an external test
• Discuss how the reusable actions affect data and
parameters.
Types of Actions
There are two kinds of actions:
• Regular (Non-reusable)
• Reusable
• Locally
• Externally
A Test with Multiple Actions
• Test data can be passed from one test to another test using the
value of an input parameter.
• This creates a data flow between business processes.
• The value passed from one business process to another will come
from the Data Table.
• Be aware of any data dependencies that occur within the
business process.
Data Table Sheets - Global
• Since there are two (or more) tests running, one right after
another, you may need to specify the iteration for each
separately.
• To affect the run settings for a particular action, set them in the
Action Call Properties dialog box.
• Right-Click on the Action label in the Keyword View, and choose
Action Call Properties from the list provided.
Defining an Action
• The Action Properties dialog box enables you to define options for
the stored action.
• You can modify an action name, add or modify an action
description, and set an action as reusable.
Passing Values to a Called
Action
• Once parameters have been set in Action Properties, you can tell
QuickTest that the parameter type being used is an Action
Parameter.
The Test Flow List