Managing DevOps Test Integrations and APIs test execution parameters in Engineering Test Management

When you are running Test Integrations and APIs tests from an IBM® Engineering Test Management server, you can send input parameters to, and receive output parameters from the agent computers that are running the tests. You can also chain together multiple Test Integrations and APIs tests in Engineering Test Management so that the output of one test can be input into another test.

About this task

The benefit to chaining tests is to pass information from one test to another. For example, you might have one test create a new user, and then pass the new (dynamic) user ID to another test, which might test deleting that user. To chain together multiple tests in Engineering Test Management, you create a test suite that contains the test cases, configure the suite to run tests sequentially, and then enable the option Pass execution variables between scripts. The name of the execution variable is important; it must be identical in all the tests that use it for chaining.

Note: You must set up the integration between Test Integrations and APIs and Engineering Test Management as described in DevOps Test Integrations and APIs and IBM Engineering Test Management.

To use input and output parameters in test execution, you perform the following high-level tasks.

Procedure

  1. Create tests in Test Integrations and APIs.
  2. Expose Test Integrations and APIs test tags as input and output.
  3. Publish the tests to an Engineering Test Management server.
  4. Run the tests on an agent computer that is registered with the Engineering Test Management server.
    The topics that follow provide an example of how to set up and use input and output parameters.