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.

Back to top

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.

Back to top

Designing Tests for LoadRunner

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 references to external actions or other external resources, such as an external Data Table file, environment variable file, shared object repositories, and so forth.

  • Include transactions in your QuickTest or Unified Functional Testing test since LoadRunner only provides performance information for data that is included within a transaction.

Back to top