Mercury QuickTest Professional 8.0 Shortcut Key Reference Card

Command Press

File Menu

New Test CTRL + N

Open Test CTRL + SHIFT + N

Business Component > New CTRL + SHIFT + O

Business Component > Open CTRL + SHIFT + E

Business Component > Edit

Template

CTRL + O

Save CTRL + S

Export to Zip File CTRL + ALT + S

Import from Zip File CTRL + ALT + O

Print CTRL + P

Edit Menu

Cut CTRL + X (EV only)

Copy CTRL + C

Paste CTRL + V

Delete DEL

Undo Ctrl + Z (EV only)

Redo CTRL + Y (EV only)

Rename Action F2

Find CTRL + F (EV only)

Replace CTRL + H (EV only)

Go To CTRL + G (EV only)

Bookmarks CTRL + B (EV only)

Complete Word CTRL + SPACE (EV only)

Argument Info CTRL + SHIFT + SPACE (EV only)

Apply “With” To Script CTRL + W (EV only)

Remove “With” Statements CTRL + SHIFT + W (EV only)

Insert Menu

Checkpoint > Standard

Checkpoint

F12

Output Value > Standard Output

Value

CTRL + F12

Step > Step Generator F7

New Step F8 (KV only)

New Step After Block SHIFT + F8 (KV only)

Key: KV = Keyword View

EV = Expert View

Test or

Component Menu

Record F3

Run F5

Stop F4

Analog Recording CTRL + SHIFT + F4

Low Level Recording CTRL + SHIFT + F3

Step

Menu

Object Properties CTRL + ENTER

Value Configuration Options CTRL + F11 on a value (KV only)

Debug Menu

Pause PAUSE

Step Into F11

Step Over F10

Step Out SHIFT + F11

Insert/Remove Breakpoint F9

Clear All Breakpoints CTRL + SHIFT + F9

Data Table Options

Edit > Cut CTRL + X

Edit > Copy CTRL + C

Edit > Paste CTRL + V

Edit > Clear > Contents CTRL + DEL

Edit > Insert CTRL + I

Edit > Delete CTRL + K

Edit > Fill Right CTRL + R

Edit > Fill Down CTRL + D

Edit > Find CTRL + F

Edit > Replace CTRL + H

Data > Recalc F9

Insert Multi-line Value CTRL + F2 while editing cell

Activate next/previous sheet CTRL + PAGEUP/

CTRL + PAGEDOWN

General Options

View Keyword View/Expert View CTRL + TAB

Open context menu for step or

Data Table cell

SHIFT + F10

or Application key ( )

Expand all branches * [on numeric keypad] (KV only)

Expand branch + [on numeric keypad] (KV only)

Collapse branch - [on numeric keypad] (KV only)

What is the extension of script and object repository files?

Object Repository : .tsr , Script : .mts, Excel : Default.xls

Object Repositories types, which & when to use?

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.

Differences between QTP & Winrunner?

• QTP is object bases Scripting ( VBS) where Winrunner is TSL (C based) Scripting.
• QTP supports ".NET" application Automation not available in Winrunner.
• QTP has "Active Screen" support which captures the application, not available in WR.
• QTP has "Data Table" to store script values , variables which WR does not have.
• Using a "point and click" capability you can easily interface with objects, their definitions and create checkpoints after having recorded a script without having to navigate back to that location in your application like you have to with WinRunner. This greatly speeds up script development.

What are the types of Object Repository’s in QTP?

QuickTest has two types of object repositories for storing object information: shared object repositories and action object repositories . You can choose which type of object repository you want to use as the default type for new tests, and you can change the default as necessary for each new test.
The object repository per-action mode is the default setting. In this mode, QuickTest automatically creates an object repository file for each action in your test so that you can create and run tests without creating, choosing, or modifying object repository files. However, if you do modify values in an action object repository, your changes do not have any effect on other actions. Therefore, if the same test object exists in more than one action and you modify an object's property values in one action, you may need to make the same change in every action (and any test) containing the object.

How QTP recognizes Objects in AUT?

QuickTest stores the definitions for application objects in a file called the Object Repository. As you record your test, QuickTest will add an entry for each item you interact with. Each Object Repository entry will be identified by a logical name (determined automatically by QuickTest), and will contain a set of properties (type, name, etc) that uniquely identify each object.
Each line in the QuickTest script will contain a reference to the object that you interacted with, a call to the appropriate method (set, click, check) and any parameters for that method (such as the value for a call to the set method). The references to objects in the script will all be identified by the logical name, rather than any physical, descriptive properties.

What is Parameterizing Tests?

When you test your application, you may want to check how it performs the same operations with multiple sets of data. For example, suppose 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.