Retrieve UFT One tests

This topic describes the administrator tasks required to retrieve UFT One tests from Jenkins.

Step 1: Upload scripts to a Git repository

Upload your UFT One scripts to a Git repository. This repository can be any Git-compliant system, whether on-premises or in the cloud.

Note: The ADM Jenkins plugin requires that the Git default branch be named master.

The UFT One scripts can reside in any directory level below master.

Back to top

Step 2: Create an API key

Generate a dedicated API key to secure the connection between Jenkins and MBT.

You generate the key for CI/CD Integration. The user performing this operation must have space admin rights. For more details, see API access.

To create an API key:

  1. In Settings > Spaces, select a space.

  2. Open the API Access tab.

  3. Click + API access to add a new API access key. Enter a name for the key, select the CI/CD integration role, and select one or more workspaces for the key.

  4. Click Add. The access key information is displayed.

    Note: For security reasons, the key information will never be displayed again, so you must record it for future use.

Back to top

Step 3: Configure the Jenkins plugin

For Jenkins to work with MBT, you need to install and configure the Application Automation Tools plugin.

To install and configure the plugin:

  1. In Jenkins, download and install the latest version of the plugin. For details, see Application Automation Tools plugin.

  2. After you install the plugin and reboot Jenkins, open Manage Jenkins > Configure system. In the ALM Octane CI section, add a new ALM Octane server and enter the following information:

    • Location: The full URL presented to you when you access MBT in ValueEdge.

    • Client ID: From the API access key.

    • Client Secret: From the API access key.

    • Jenkins User: The Jenkins user that runs the MBT jobs.

  3. Click Test Connection to make sure Jenkins connects with MBT.

Back to top

Step 4: Configure MBT

To complete the setup, you need to set up Jenkins connectivity from the MBT side, and define an MBT runner and release.

  1. In Settings >Spaces, select a workspace.

  2. Open the DevOps tab.

  3. Open the CI Servers section and click + CI Server to add a new CI server.

  4. Enter a name for the CI server, and select your Jenkins server from the CI Server list.

    Note: If your Jenkins server does not appear on this list, either the Jenkins side is not defined correctly (Test Connection on Jenkins has failed), or this Jenkins server is already used by another MBT CI Server setup.

  5. Define the MBT Runner. This links the Jenkins server with the Git repository, generates the Git auto-discovery (mirroring) jobs, and defines and launches MBT tests on the Jenkins server.

    1. Open the Test Runners section and click + Test Runner to add a new test runner.

    2. Define the following:

      • Name: Enter a name for the runner.

      • Framework: Select MBT.

      • CI server: Select the CI server that you added.

      • Repository: Enter the URL of your Git repository.

      • Username and Password: Enter the credentials needed to connect to the Git repository (read-only access).

      Click Test Connection to validate that all settings are correct.

  6. Open the workspace Releases tab and make sure that at least one release is defined, as MBT requires each test run to be associated with a release.

Back to top

See also: