Running tests in Server-Side Execution

Relevant for: GUI tests and API testing

Run tests in server-side execution when the tests are saved on a Lab Management-enabled ALM server. Server-side execution enables ALM to run UFT tests on remote hosts at predefined times or on an ad-hoc basis, without anyone logged in to the host to initiate and control the test runs. By contrast, client-side execution requires a user to be logged in to the host computer on which ALM runs the UFT test.

To set up server-side execution on ALM:

  1. In the Testing > Test Lab module, create functional test sets. A functional test set is a group of automated tests or test configurations in an ALM project, designed to achieve a specific goal.

  2. In the Lab Resources > Testing Hosts module, select hosts upon which the tests can run remotely.

  3. If you want to use different values for specific parameters when running the tests on different environments or situations, you can define AUT parameters in the Lab Resources > AUT Environments module.

  4. In the Testing > Timeslots module, schedule automatic test runs, or reserve timeslots to use for running manually.

    Tip: You do not need to reserve a timeslot if you run the tests ad-hoc.

For additional information, see the Application Lifecycle Management User Guide.

In UFT, you can link your test parameters to ALM AUT Environment parameters. This enables the test to use AUT environment parameter values passed from ALM when your UFT test runs in server-side execution. For details, see AUT environment parameters.

Note: Server-side execution is available only for ALM Edition and Performance Center Edition, version 11.50 or later. You must also have Lab Management support for the ALM project.

For task details, see Run a test using Server-Side Execution.