You can run UFT 12.02 scripts in Performance Center 12.20 as part of a test if you Have:

1. a ''GUI Vusers'' license for each Vuser
2. a UFT license for each Vuser
3. a standalone LG with UFT 12.02 installed

HP Functional Testing software (QuickTest or Unified Functional Testing) enables you to create complex tests that examine the full spectrum of your application's functionality.

LoadRunner can integrate QuickTest or Unified Functional Testing tests into a load testing scenario in the form of GUI Vuser scripts. These tests, that have already been designed and debugged in QuickTest or Unified Functional Testing can be used as the basis of your load test.

The main uses of running QuickTest or Unified Functional Testing tests in LoadRunner are:

*To check how your application's functionality is affected by heavy load

*To measure the response time that a typical user experiences on the client side while your application is under load (end-to-end response time)

For example, you can add QuickTest or Unified Functional Testing tests to specific points in a LoadRunner scenario to confirm that the application's functionality is not affected by the extra load at those sensitive points.

Another advantage of using a GUI Vuser script as part of your LoadRunner scenario is that the GUI Vuser script runs on your screen during the scenario, enabling you to watch the actual steps executed by the Vuser in real time.

**Guidelines for Using QuickTest or Unified Functional Testing Tests in LoadRunner**

When creating test scripts in QuickTest or Unified Functional Testing that are going to be used as GUI Vuser scripts in a LoadRunner testing scenario, you need to follow certain guidelines to ensure smooth integration of the script. For detailed explanations about creating tests in QuickTest or Unified Functional Testing, see the QuickTest or Unified Functional Testing documentation.

**Limitations**

QuickTest or Unified Functional Testing offers several features that are designed specifically for integration with LoadRunner. Some QuickTest or Unified Functional Testing features, however, may not be available when they are integrated with LoadRunner. For more information about specific limitations, see the QuickTest or Unified Functional Testing readme.

**Including Transactions**

To measure the performance of the server, you define transactions. A transaction represents an action or a set of actions that you are interested in measuring. You define transactions within your Vuser script by enclosing the appropriate sections of the script with start and end transaction statements.

For example, you can define a transaction that measures the time it takes for the server to process a request to view the balance of an account and for the information to be displayed at the ATM.

Note: LoadRunner only provides performance information for data that is included within a transaction. Therefore, your QuickTest or Unified Functional Testing test must include transactions to be used by LoadRunner.

For more information about using transactions in QuickTest or Unified Functional Testing, see the QuickTest or Unified Functional Testing documentation.

**Adding Statements**

You can use the Services object and its associated methods to insert statements that are specifically relevant to performance testing. These include Abort, GetEnvironmentAttribute, LogMessage, SetTransactionStatus, ThinkTime, UserDataPoint, StartTransaction and EndTransaction. For more information on these methods, see the QuickTest or Unified Functional Testing documentation.

**Designing Tests for LoadRunner & Performance center**

Consider the following design guidelines when designing tests for use with LoadRunner:

*The QuickTest or Unified Functional Testing tests you use with LoadRunner should be simple tests, designed to pinpoint specific operations.

***LoadRunner cannot run nested action iterations.**

***Do not include re

Manas_Ranjan

Please look closely at the bulk ''upload script(s)'' dialog box. There is at warming stating

***'' Only zipped VuGen scripts can be uploaded. Uploading QTP or ST tests will result in failure''***

This means you can only upload **VuGen** scripts using this method. Use the UFT program to upload your UFT (QTP) scripts.

In UFT:

- Connect to **ALM** ( UFT menu bar --> ALM... )
- Save your sscript to the **ALM folder** ( File --> Save As..--> select the ALM folder ...)