Integration with Performance Testing products or Business Process Monitor

Precautions/considerations to take when integrating QuickTest Professional (QTP) / Unified Functional Testing (UFT) with Performance Testing products or Business Process Monitor (BPM)

Designing considerations

•Performance Testing products (LoadRunner – LR)

1.QTP/UFT tests used with LR and Performance Center (PC) should be simple and designed to pinpoint specific operations. Also, when working with action iterations, corresponding StartTransaction and EndTransaction statements must be contained within the same action.

2.Every QTP/UFT test must contain at least one transaction to provide useful information in the performance test. LR and PC use only the data that is included within a transaction, and ignore any data in a test outside of a transaction.

3.Do not include references to external actions or other external resources (including resources stored in Quality Center – QC / Application Lifecycle Management – ALM), such as an external data table file, environment variable file, shared object repositories, function libraries, and so forth. This is because LR or PC may not have access to the external action or resource.

Note: if the resource can be found on the network, QTP/UFT will use it. For example, you can try defining external resources via an absolute path, or by adding them as supplementary files and transferring them to Load Generator in the QTP/UFT test folder.)

4.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.

•Business Process Monitor (BPM) / Business Service Management (BSM) / Business Availability Center (BAC)

Note: As of BSM 9.0, profiles are no longer used. Instead, BPM uses "Business Transaction Flows", which are included in the parent application’s run unit and can be run as part of that unit or independently, as needed.

1.All considerations when running on "Performance Testing products", should be consider on this as well.

2.When measuring a distributed transaction:

· over two different BPM profiles or Business Transaction Flows (depending on the version), the profile with the StartDistributedTransaction statement must be run before the profile with the associated EndDistributedTransaction.

· over two BPM profiles, make sure that the timeout value specified is large enough so that the profile or Business Transaction Flow (depending on the version) containing 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.

· make sure that to relate the tests to a single BPM instance. BPM 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.

Running tests considerations

•Performance Testing products (LR)

1.Can run only one GUI Vuser concurrently per computer. (A GUI Vuser is a Vuser that runs a QTP/UFT test.)

2.Ensure that QTP/UFT is closed on the QTP/UFT computer before running a QTP/UFT test in PC or LR.

3.The settings in the LR or PC Run-time Settings dialog box are not relevant for QTP/UFT tests.

4.Cannot use the ResultDir QTP/UFT environment variable when running a performance test.

5.Transaction breakdown is not supported for tests (scripts) created with QTP/UFT.

6.QTP/UFT cannot run on a computer that is:

· logged off or locked. In these cases, consider running QTP/UFT on a terminal server.

· already running a QTP/UFT test. Make sure that the test is finished before starting to run another QTP/UFT test.

7.Ensure the LR agent is setup to run as process, not service.

•Business Process Monitor (BPM) / Business Service Management (BSM) / Business Availability Center (BAC)

1.Check which versions of QTP/UFT are supported by desired PBM version. For information see BPM documentation or "Integration Matrix" section below

2.QTP must be installed and closed on the BPM computer

3.BPM can run only one QTP/UFT test at a time. Make sure that the previous QTP/UFT run session is finished before starting to run another QTP/UFT test.

4.QTP/UFT tests must be zipped before uploading them to BSM Admin. If changes are made to local copy of a QTP/UFT test after uploading it, re-upload updated zipped test again.

5.Cannot use the ResultDir QTP/UFT environment variable when running a test in BPM.

6.Transaction breakdown is not supported for tests created with QTP/UFT .

7.QTP/UFT cannot run tests on a computer that is:

1.Logged off

2.Locked

3.Running QTP/UFT as a non-interactive service.

Debugging Scripts Considerations

1.Ensure the QTP/UFT test complies strictly with all items from above sections ("Designing considerations" and "Running tests considerations") for respective product.

2.Confirm versions of the products are compatible. For more information see "Integration Matrix" below

3.Confirm script execution with QTP/UFT’s tool, called "Silent Test Runner", runs without problems.

Note: If the script encounters problems/errors on the log, there is high probability running the same script from BPM/LR/PC will also return errors.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s