QuickTest Tests for Use with LoadRunner or Business Process Monitor

Advertisement:

QuickTest Tests for Use with LoadRunner or Business Process Monitor: The QuickTest tests you use with LoadRunner or Business Process Monitor should be simple, designed to pinpoint specific operations, and should avoid using external actions and references to other external files (including resources stored in Quality Center). Also, when working with action iterations, corresponding StartTransaction and EndTransaction statements must be contained within the same action.


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

1. Do not include references to external actions or other external resources (including resources stored in Quality Center), such as an external Data Table file, environment variable file, shared object repositories, function libraries, and so forth. This is because LoadRunner may not have access to the external action or resource. (However, if the resource can be found on the network, QuickTest will use it.)

2. Every QuickTest test must contain at least one transaction to provide useful information in LoadRunner.

3. Make sure that the last step(s) in the test closes the application being tested, as well as any child processes that are running. This enables the next iteration of the test to open the application again.

Designing Tests for Business Process Monitor: Consider the following guidelines when designing tests for use with Business Process Monitor:

1. Every QuickTest test must contain at least one transaction to provide useful information in Business Process Monitor.

2. When measuring a distributed transaction over two different Business Process Monitor profiles, the profile with the StartDistributedTransaction statement must be run before the profile with the associated EndDistributedTransaction.

3. When measuring distributed transactions, make sure that you relate the tests to a single Business Process Monitor instance. Business Process Monitor searches for the end transaction name in all instances, and may close the wrong distributed transaction if it is included in more than one instance.

4. When measuring a distributed transaction over two Business Process Monitor profiles, make sure that the timeout value you specify is large enough so that the profile that contains the StartDistributedTransaction step and all the profiles that run before the profile that contains the EndDistributedTransaction step, will finish running in a time that is less than the value of the specified timeout.

5. Business Process Monitor does not support running QuickTest Professional tests that require access to external resources, including resources stored in Quality Center (such as a shared object repository, function library, external Data Table, external actions, and so forth). Tests that require external resources may fail to run on Business Process Monitor. (However, if the resource can be found on the network, QuickTest will use it.)

6. Make sure that the last step(s) in the test closes the application being tested, as well as any child processes that are running. This cleanup step enables the next test run to open the application again.
Advertisement:

175248765853890