Run GUI tests from performance testing products

Relevant for: GUI tests only

This topic describes how to run GUI tests in OpenText Enterprise Performance Engineering and OpenText Enterprise Performance Engineering.

Considerations

Consider the following guidelines when running tests from performance testing products

  • You can run only one GUI Vuser concurrently per computer. (A GUI Vuser is a Vuser that runs a GUI test.)

  • Ensure that OpenText Functional Testing is closed before running a test in OpenText Enterprise Performance Engineering or OpenText Enterprise Performance Engineering.

  • The settings in the OpenText Enterprise Performance Engineering or OpenText Enterprise Performance Engineering Run-time Settings dialog box are not relevant for OpenText Functional Testing tests.

  • You cannot use the ResultDir environment variable when running a performance test.

  • Transaction breakdown is not supported for tests (scripts) created with OpenText Functional Testing.

  • OpenText Functional Testing cannot run on a computer that is already running a test. Make sure that the test is finished before starting to run another test.

  • To run tests on a computer that is logged off or locked, configure OpenText Functional Testing for logged off remote connections. For details, see Run a test from a remote computer.

Back to top

Insert and run the GUI test

You can insert and run GUI tests in OpenText Enterprise Performance Engineering and OpenText Enterprise Performance Engineering.

Insert a test in an OpenText Professional Performance Engineering scenario

In the Controller Open Test dialog box, browse to the test folder. In the Files of type box, select Unified Functional Testing Tests. This enables you to view the tests in the folder.

Use a test in OpenText Enterprise Performance Engineering

Create a zipped version of an OpenText Functional Testing test, and upload it to the OpenText Enterprise Performance Engineering User Site Vuser Scripts page.

Run multiple GUI Vusers on the same application

Open a terminal server session for each GUI Vuser. For details, refer to the performance testing documentation.

Back to top

See also: