OpenText Functional Testing tests

This topic describes how to run OpenText Functional Testing GUI and API tests from OpenText Enterprise Performance Engineering.

Prerequisites

Below is a list of prerequisites that are required to run OpenText Functional Testing GUI or API tests from OpenText Enterprise Performance Engineering.

OpenText Functional Testing GUI
  • To run OpenText Functional Testing tests from OpenText Enterprise Performance Engineering you need a LoadRunner GUI Virtual User bundle license.

  • To create a GUI test in OpenText Functional Testing, make sure that you allow OpenText Functional Testing to interrupt the desktop.

  • To check the PASS/FAIL criteria of checkpoints in OpenText Enterprise Performance Engineering, you need to surround them with transactions because OpenText Functional Testing checkpoints are not recognized by OpenText Enterprise Performance Engineering.

    Example:“Services.StartTransaction "transaction1"/ Services.EndTransaction "transaction1"

    These transactions are displayed when the test is run. If, for example, a verification point is valid, the transactions are passed.

OpenText Functional Testing API

If you want to run a OpenText Functional Testing API load test in OpenText Enterprise Performance Engineering, you need to convert the script in UFT to an API Load Test. For details, see Prepare and run a Load test in the UFT documentation.

Note: The file path inside a script folder must not exceed 260 characters.

Back to top

Set up and run a OpenText Functional Testing test

This task describes how to run OpenText Functional Testing GUI and API tests from OpenText Enterprise Performance Engineering.

  1. Upload OpenText Functional Testing tests to OpenText Enterprise Performance Engineering.

    For details, see Upload a script.

    After uploading the script to OpenText Enterprise Performance Engineering, the script is added to the test management tree. You can view and edit most scripts directly from within the OpenText Enterprise Performance Engineering user interface. For details, see Edit a script.

  2. Create a OpenText Enterprise Performance Engineering test, and assign the OpenText Functional Testing test to it.

    For details, see Tests.

  3. Set the number of Vusers per group to run the script.

    Script Type Description
    GUI

    Typically, set this number to 1, because OpenText Functional Testing does not support running multiple instances on the same Windows session.

    However, if you want to run multiple Vusers on the same load generator, you can do so by using the LoadRunner-Terminal Services integration. This enables you to create multiple Windows sessions on the same load generators, and as a result, run one OpenText Functional Testing GUI Vuser on each Windows session.

    API

    API tests do not have the same constraints as GUI tests in relation to the number of Vusers that can be run per load generator.

  4. Select the machine on which OpenText Functional Testing is installed as the load generator.

    Note: Make sure that you restart the load generator after installing OpenText Functional Testing.

    For details, see Tests.

  5. Run the test.

    For details, see Manage a performance test run.

Back to top

Notes and limitations

OpenText Functional Testing (GUI) scripts can run with Network Virtualization with Per Load Generator mode only; they cannot run with Per Group mode.

Back to top

See also: