Shortcut Key Function for recording options in Quick Test Professional :

Record - F3 - Starts recording mode.
Run - F5 -Runs the test from the beginning or from the line at which the test was paused.
Stop - F4 - Stops test recording or the test run.
Analog Recording - CTRL + SHIFT + F4 -Starts/ends analog recording mode.
Low Level Recording - CTRL + SHIFT + F3 Starts/ends low level recording mode.

Adding Test Object Properties to the Properties List

You can add a valid test object property to the object properties list in the Add/Remove dialog box. Suppose you want QuickTest to use a specific property to identify your object, but that property is not listed in the properties list. You can open the Add Property dialog box and add that
property to the list.

Changing the Active Screen
As the content of your application or Web site changes, you can continue to use tests you developed previously. You simply update the selected Active Screen display so that you can use the Active Screen to add new steps to your test rather than re-recording steps on new or modified objects.

Creating Tests with Locked Resources
If your QuickTest settings have been configured to use a default, shared object repository file, any test you create is automatically associated with that external file for all test object information. When you create a new test, the shared object repository file may be locked

Creating Synchronization Points

If you do not want QuickTest to perform a step or checkpoint until an object in your application achieves a certain status, you should insert a synchronization point to instruct QuickTest to pause the test until the object property achieves the value you specify (or until a specified timeout is exceeded).

Adding Exist and Wait Statements

You can enter Exist and/or Wait statements in the Expert View to instruct QuickTest to wait for a window to open or an object to appear.

Measuring Transactions

You can measure how long it takes to run a section of your test by defining transactions. A transaction represents the business process that you are interested in measuring. You define transactions within your test by enclosing the appropriate sections of the test with start and end transaction statements.

Checkpoint timeout

Specifies the time interval (in seconds) during which QuickTest attempts to perform the checkpoint successfully. QuickTest 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.

Insert statement for checkpoints

Specifies when to perform the checkpoint in the test. Choose Before current step if you want to check the value of the object property before the highlighted step is performed. Choose After current step if you want to check the value of the object property after the highlighted step is performed.

QTP testing process

1. Preparing to recording
2. Recording
3. Enhancing your script
4. Debugging
5. Run
6. Analyze the result
7. Report Defects

Differences between QTP & Winrunner

1. QTP is object bases Scripting ( VBS) where Winrunner is TSL (C based) Scripting.
2. QTP supports ".NET" application Automation not available in Winrunner
3. QTP has "Active Screen" support which captures the application, not available in WR.
4. QTP has "Data Table" to store script values, variables which WR does not have.
5. QTP does not support in Firefox browser.

Toolbars in QTP

QuickTest has 4 built-in toolbars:
1. The File toolbar
2. The Testing toolbar
3. The Debug toolbar
4. Action toolbar
The Action toolbar is available in the Keyword View and contains options that enable you to view all actions in the test flow or to view the details of a selected action. The Action toolbar is not available for components.

Scripting languages Support in QTP

Visual Basic (VB), XML, JavaScript, Java, HTML

Types of Actions in QTP

There are three kinds of actions:

1. non-reusable action—an action that can be called only in the test with which it is stored, and can be called only once.
2. reusable action—an action that can be called multiple times by the test with which it is stored (the local test) as well as by other tests.
3. external action—a reusable action stored with another test. External actions are read-only in the calling test, but you can choose to use a local, editable copy of the Data Table information for the external action.

Supported Add-ins :

The following external QuickTest 6.5.x add-ins are supported for use with QuickTest Professional 8.0:

• Java Add-in 6.5
• Oracle Add-in 6.5
• PeopleSoft Add-in 6.5
• Terminal Emulator Add-in 6.5
• .NET Add-in 6.5.1
• SAP solutions Add-in 6.5.1

Supported Environments and Programs :

QuickTest Professional 8.0 supports creating, recording, and running tests or components using the environments and programs described below.
Standard Windows Applications
1.Win32 API
2.MFC
Visual Basic Applications
Visual Basic 6.0

Note: Visual Basic .NET applications are supported by the QuickTest Professional .NET Add-in.

Browsers

• Microsoft Internet Explorer 5.5 Service Pack 2-6.0 (required)
• Netscape 6.1, Netscape 6.22, Netscape 6.23, Netscape 7.02, and

Netscape 7.1 (optional)

• AOL 8.0 and 9.0 (optional)


- Vignesh

hui guys

can anybody explain about QTP Smart Identification & Spy?

- vignesh

Types of Checkpoints:

In QTP the following types of checkpoints can be inserted to check various objects in a Web site or application.

Standard Checkpoint checks the property value of an object in your application or Web page. The standard checkpoint checks a variety of objects such as buttons, radio buttons, combo boxes, lists, etc. For example, you can check that a radio button is activated after it is selected or you can check the value of an edit field.

Note: Standard checkpoints are supported for all add-in environments

Image Checkpoint checks the value of an image in the application or Web page. For example, we can check that a selected image's source file is correct.

Note: Image checkpoint can be created by inserting a standard checkpoint on an image object.

Bitmap Checkpoint checks an area of a Web page or an application as a bitmap. For example, consider a Web site that can display a map of a city the user specifies. The map has control keys for zooming. We can record the new map that is displayed after one click on the control key that zooms in the map. Using the bitmap checkpoint, we can check that the map zooms in correctly.

Note: Bitmap checkpoints are supported for all add-in environments

Table Checkpoint checks information within a table. For example, suppose an application or Web site contains a table listing all available flights from New York to San Francisco. You can add a table checkpoint to check that the time of the first flight in the table is correct.

Note: You create a table checkpoint by inserting a standard checkpoint on a table object

Text Checkpoint checks that a text string is displayed in the appropriate place in the application or a Web page. For example, consider an application or Web page that displays the sentence Flight departing from New York to San Francisco. We can create a text checkpoint that checks that the words "New York" are displayed between "Flight departing from" and "to San Francisco".

Note:Text checkpoints are supported for all add-in environments

Text Area Checkpoint checks that a text string is displayed within a defined area in a Windows application, according to specified criteria. For example, suppose your Visual Basic application has a button that says View Doc <Num>, where <Num> is replaced by the four digit code entered in a form elsewhere in the application. You can create a text area checkpoint to confirm that the number displayed on the button is the same as the number entered in the form.

Note: Text area checkpoints are supported for Standard Windows, Visual Basic, and ActiveX add-in environments Text area checkpoints are also supported for some external add-in environments.

Accessibility Checkpoint identifies areas of your Web site that may not conform to the World Wide Web Consortium (W3C) Web Content Accessibility Guidelines. For example, guideline 1.1 of the W3C Web Content Accessibility Guidelines requires you to provide a text equivalent for every non-text element. You can add an Alt property check to check whether objects that require the Alt property under this guideline, do in fact have this tag.

Note: Accessibility checkpoints are supported for the Web environment

Page Checkpoint checks the characteristics of a Web page. For example, you can check how long a Web page takes to load or whether a Web page contains broken links.

Note: You create a page checkpoint by inserting a standard checkpoint on a page object.

Page checkpoints are supported for the Web environment

Database Checkpoint checks the contents of a database accessed by your Web site. For example, you can use a database checkpoint to check the contents of a database containing flight information for your Web site.

Note: Database checkpoints are supported by all environments.

XML Checkpoint checks the data content of XML documents in XML files or XML documents in Web pages and frames. XML checkpoints (Web page/frame) are supported for the Web environment; XML checkpoints (file) are supported by all environments

- Vignesh

Hui

"How to connect to the Database from QTP?"

- Vignesh

Hui

"How to retrieve the data from database?"

- Vignesh