Run UFT One tests from the ALM Test Lab

Use Bamboo to trigger a UFT One test run for a test in the ALM Test Lab.

To run UFT One tests from the ALM Test Lab:

  1. (Optional) You may want to configure the environment details for the application being tested before you run the test. To do this, add an additional build task to your build plan.

    For details, see Configure the application environment.

  2. In your build plan, add an additional task.

    In the task types window, open the Tests pane and select the UFT One ALM Lab Management task.

    A new, empty task is added as part of your build plan.

  3. Provide the following information for your task:

    Task description (optional) A description to understand the purpose of the task.
    ALM Server

    The ALM server from which to run the test.

    The ALM server address must be in the format: http://<ALM server name or IP>:<port>/qcbin.
    ALM Connectivity

    Depending on the authentication type required by your ALM server, credentials can be a username and password or an API key for SSO authentication.

    • Username and password:

      User name: The ALM user name to use to access the server.

      Password: The password for the ALM user specified above.

    • SSO authentication (ALM 15.5 or later, UFT One Bamboo plugin version 1.6 or later):

      Select SSO enabled.

      Enter the Client ID and Api Key Secret obtained from your ALM site administrator.

    Ensure that the ALM user or client specified in this task has the correct permissions to open and run the UFT One tests.

    For details on permissions, see the ALM Help Center.
    Domain The domain in the ALM server where the project containing the tests is stored.
    Project

    The project containing the tests.

    The selected project should be enabled for Server Side Execution of UFT One tests.

    For details on Server Side Execution, see the Application Lifecycle Management User Guide.
    Run type

    Select one of the following types of runs:

    • Test set

    • Build verification suite

    For more details about test steps and build verification suites, see the Application Lifecycle Management User Guide.
    Test Set/Build Verification Suite ID

    The ALM ID of the selected test set or the build verification suite ID.

    If you select a test set, your test set should be a functional test set, and must be prepared for Server Side Execution.

    For details, see the Application Lifecycle Management User Guide
    Description The description of the test set or build verification suite (as entered in ALM).
    Timeslot Duration The duration of the slot reserved for a scheduled run of the test set or build verification suite.
    Environment Configuration ID

    The ID of your application environment configuration, as entered in ALM.

    To find this ID, in ALM, right-click the entity, copy the URL, and paste it to a text editor.

    Use the number associated with the EntityID at the end of the URL.

  4. Save the configuration.

    When the build runs, the test will run as a build task with the specified settings.

    After the test run, the relevant build logs are saved in the Logs tab of the build execution results. You can view details about the test run and links to run results.

    The run result file name includes a timestamp of the run, which matches the Bamboo system variable bamboo.buildTimeStamp. This enables you to more easily refer to a specific result file in an automation script.

Back to top