Set up UFT integration

This topic explains how to integrate ALM Octane with UFT via Jenkins or Bamboo. This integration enables ALM Octane to reflect the UFT tests from your Source Code Management (SCM) repository as executable automated tests. You can then include and run these UFT tests in test suites.

ALM Octane-UFT integration flow

Once the UFT integration is set up, the CI server and the SCM system are transparent and you can work with UFT and ALM Octane directly: 

  • Create and edit your tests and their data tables in UFT and save them in a Git or SVN repository.
  • Run the tests and track their results in ALM Octane.

The ALM Octane-UFT integration flow includes the following:

Set up. To set up the integration, create a CI server and a testing tool connection in the ALM Octane settings. This process is described in the sections below.

ALM Octane discovers UFT tests and data tables. ALM Octane creates automated test entities to represent the GUI and API UFT tests stored in your repository.

ALM Octane periodically checks for changes in the repository.

Associate tests with ALM Octane entities. Associate the tests with your backlog and application modules. This helps you use the test run results in ALM Octane to track your product and release quality.

Run tests. Include the tests in test suites to plan and run them from ALM Octane. ALM Octane triggers the test runs via the CI server. The tests run on UFT machines configured as Jenkins execution nodes.

Analyze release and product quality. Track the UFT test results as part of the overall data in the backlog, quality, and dashboard modules.

The image below summarizes the architecture of this integration (with Jenkins):

Back to top

Before you set up the integration

Set up UFT to store tests and data tables in a Git or SVN repository. For details, see the UFT Help Center.

Note:  

  • UFT-SCM integration is supported for UFT 12.50 and later.
  • For ALM Octane to locate the data tables in your repository, store them in an entirely separate folder from your tests.

Back to top

In your CI server, set up the connection to ALM Octane

Back to top

In ALM Octane, add your CI server

  1. In ALM Octane, click Settings , select Spaces and select a workspace.

  2. Select the DevOps > CI Server tab.

  3. Add a CI server and select your CI server's URL.

For more details, see Add CI servers on ALM Octane.

Back to top

Create a UFT test runner in ALM Octane

  1. In ALM Octane, click Settings , select Spaces and select a workspace.

    Tip: You can only define one UFT test runner per workspace.

  2. Select the DevOps > Test Runners tab.

  3. Click + Test Runner.

  4. Name the test runner entity that ALM Octane will use to run the UFT tests, and select the UFT framework.

  5. Select your CI server.

    The list displays all servers that meet the following conditions:

    • The server has the ALM Octane CI plugin installed and configured to access your ALM Octane.

    • The API Access keys that the plugin is using are assigned the CI/CD Integration role in the current workspace.

  6. Specify the type and URL of the SCM repository that contains your UFT tests and data tables.

  7. If required, provide the authentication details for your repository.

  8. Click Test Connection to make sure the configuration is correct.

  9. Click Save and Connect to complete the connection.

  • If you are integrating via Bamboo, ALM Octane creates two plans: UFT test discovery that connects to the repository and discovers the UFT tests and data tables, and UFT test executor that runs the tests.

  • If you are integrating via Jenkins, ALM Octane creates a Jenkins job that connects to the repository and discovers the UFT tests and data tables.

Tip: If necessary for troubleshooting, you can find this job on your CI server based on the connection ID.

To enable test execution, see Enable the CI server to trigger UFT test runs.

The test scripts and the data table content are available in UFT only.

What will you see in the Tests tab?

In the automated test entities in ALM Octane, the following fields are set:

  • Testing tool type = UFT

  • Test type = API or UI

  • Executable = Yes. These tests can be added to test suites and run from ALM Octane.

If you do not see all of the expected tests in the Tests tab in ALM Octane, try refreshing the list of tests.

What happens when a test is changed in UFT?

ALM Octane continues to periodically check the repository and updates its entities as follows:

  • If you add a new test in UFT or change an existing one, the changes are reflected in ALM Octane.

  • If you delete a test from UFT, the relevant test in ALM Octane is not deleted but is marked as not executable. This way, the test and its history, runs, and reports remain available.

  • If you rename a UFT test in GIT, the test is renamed in ALM Octane if your ALM Octane version is 12.60.3 or later, and the test was committed without additional changes.

  • If you rename a UFT test in SVN, or if you rename in GIT and do not fill the above conditions, a new test is created in ALM Octane and the original test is marked as not executable

Back to top

Enable the CI server to trigger UFT test runs

Back to top

Next steps: