DevOps test tools integration overview

In IBM® Engineering Test Management, you can manage and run tests that were created by automated test tools.

When you run an automated test, Engineering Test Management sends commands to the machines in your test lab that run the automated tests and show the test results in your browser.

After you create a reference to an automated test, you can associate it with a test case in Engineering Test Management. You can then generate a test case execution record for that test case and run the test.

Each test tool implements its own integration with Engineering Test Management. Although most integrations are similar, the instructions that are provided here do not cover every detail of each integration. For more information, see the documentation for the test tool that you are integrating with.

Test tool adapters

Automated test tools integrate with Engineering Test Management by using adapters. Each adapter serves as a bridge between the test tool and Engineering Test Management. The adapter listens to requests from Engineering Test Management and then runs tests on the test machine where the test tool is installed.

Usually, the adapter is installed with its closely related product. For example, the DevOps Test Performance adapter is installed with DevOps Test Performance, which runs on the test machine for Performance Tester in the lab. Any configurations to the adapter are done on the machine where the product is installed.

Exception: The HCL Security AppScan adapter is a special case. That adapter runs on the Engineering Test Management server, not on an HCL Security AppScan test machine.

To connect an adapter to an Engineering Test Management server, you can use any of these adapters. To determine which version of the adapter is compatible with Engineering Test Management, see the adapter documentation:

  • HCL Security AppScan Tester Edition, using the adapter files that come with Engineering Test Management
  • IBM DevOps Test UI
  • IBM DevOps Test API
  • IBM DevOps Test Performance
  • IBM DevOps Test Workbench
  • IBM DevOps Test Embedded
  • DevOps Service Tester

When you are using a third-party test execution adapter, to determine which version of the adapter is compatible with Engineering Test Management, see the adapter documentation.

Restriction: Smart cards and SSL certificates are not supported as authentication types for test tool adapters. Only user ID and password authentication is supported.

User accounts to run the test tool adapter

Each test tool adapter is associated with a user account that has the repository permissions, licenses, project area membership, and roles to run the adapter. The user account for an adapter must meet these requirements:
  • Have the JazzUsers repository permission
  • Have an assigned Engineering Test Management - Quality Professional or Engineering Test Management - Connector client access license
  • Be a member of the project area that the adapter is connecting to
  • Be assigned the Test Team Member role, not the Test Team Contributor role
Tip: You can create a separate user account that is used only to run test tool adapters.

Managing automated tests that are local to a test machine

To use the adapters to run automated tests that are local to a test machine, these requirements must be met:

  • The Engineering Test Management web client and server must be running.
  • Except in the case of HCL Security AppScan Tester Edition, the adapter must be installed and running on the same machine as its corresponding test tool.
  • Test scripts and other test artifacts must be on the local test machine where you are going to run the tests.

The following diagram shows a request to run an automated test when the test resources are already on a test machine. The process is the same for the other test tools, except for HCL Security AppScan Tester Edition.

Table 1.
Process Flow Explanation
Integration between Engineering Test Management, the Functional Test adapter, and the test machine
  1. You request the IBM DevOps Test UI adapter to run an automated functional test that is stored on a local test machine.
  2. The IBM DevOps Test UI receives the request and initiates a test run on the test machine.
  3. The test runs on the test machine, and the adapter sends the results back to the Engineering Test Management server.
  4. You can view the test run and its results in the web client.

For more information, see the related help topic about creating a reference to an automated test script on a local test machine.

Managing automated tests that are stored at a shared location

In Engineering Test Management, you can specify that test resources must be copied from a shared location to a local test machine where the test is run. When you create the test script, you specify the shared location where the test resources are stored. When you run the test, you specify the test machine where the test is to run. The test resources are copied to that machine. Finally, the adapter on that machine runs the test by using a copy of the test resources.

Note: Before you can use shared test resources, an administrator must make the resources available to Engineering Test Management. After the shared resource are available, team members can create test scripts that reference that resource.

The following diagram shows a user request to run an automated test that is stored at a shared network location:

Table 2.
Process Flow Explanation
Integration with an automated test that is stored on a shared test resource
  1. You request to run an automated functional test that is stored at a shared network location.
  2. The IBM DevOps Test UI receives the request and copies the test from the shared location to the functional test machine.
  3. The test runs on the test machine, and the adapter sends the results back to the Engineering Test Management server.
  4. You can view the test run and its results in the web client

For more information, see the related help topic about creating a reference to an automated test script at a shared location.