Run UFT tests from Performance Center

This topic describes how to run UFT GUI and API tests from Performance Center.


Below is a list of prerequisites that are required to run UFT GUI or API tests from Performance Center.

Script Type Description
  • To run UFT tests from Performance Center, you need a LoadRunner GUI Virtual User bundle license.

  • Create a GUI test in UFT.

    • When creating a GUI test, make sure you allow UFT to interrupt the desktop.

    • UFT checkpoints are not recognized by Performance Center. Therefore, if you want to check the PASS/FAIL criteria of checkpoints in Performance Center as well, you need to surround them with transactions.


      “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 will be passed.


Create an API test in UFT. For details, see the UFT documentation.

Back to top

Run a UFT test from Performance Center

  1. Connect your UFT with the same ALM instance as Performance Center (this can be done from the ALM tab in UFT). Save the UFT test in ALM.

  2. Create a Performance Center test, and assign the UFT test to it.

    For details, see Design a performance test.

  3. Set the number of Vusers per group that will run the script.

    Script Type Description
    • Typically, this number should be set to 1, because UFT 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 UFT GUI Vuser on each Windows session.

    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 UFT is installed as the load generator.

  5. Run the test.

    For details, see Manage a performance test run.

Back to top

See also: