Creating references to automated test scripts on a local test machine

With IBM® Engineering Test Management, you can create a reference to an automated test script on a test machine in your test lab.

Before you begin

Before you can create a reference to an automated test script on a local lab machine, the appropriate adapter must be running. See the section on Integrating with Rational test tools for information about starting the adapters.

Note: Each test tool implements its own integration with Engineering Test Management. The instructions that are provided here might not cover all details of each integration. Be sure to refer to the specific test tool for further details.

Procedure

To create a reference to an automated test script on a local lab machine:

  1. In the main menu, click Construction > Create > Test Script.
  2. Type a name for the new test script.
    Tip: Be sure to use a name that is the same or similar to the name of the actual test script.
  3. Click <Click here to enter a description> to enter a description of the new test script reference.
  4. Select one of the following test script types:
    • IBM Security AppScan® Tester Edition
    • Rational Functional Tester
    • Rational Performance Tester
    • Rational Service Tester
    • Rational Test Workbench
  5. Optional: To assign execution of this script to a specific machine, click the Edit icon next to Preferred machine. When the automated script runs, this machine is preferred when it is available to run the script.
  6. In the Script Details section, select Use test resources that are local to a test machine.
  7. Click the Select Adapter button.
  8. Select the appropriate adapter from the list of adapters.
    Note: The green icon under the State column indicates that the adapter is running.
    Note: To designate a preferred machine to be used at execution time, select the When the selected machine is available, use it as the preferred machine to run the test scripts option.
  9. Provide the project path on the test machine to where the test script is located.
    For example, c:\workspaces\rft1\Altoro1.
    Note: For some tools, such as Rational® Functional Tester, providing the project path means the full file system path.

    For Rational Performance Tester and Rational Service Tester for SOA Quality, this path includes the project name that is in the workspace that is associated with the adapter.

    If the Rational Performance Tester project is not in the same workspace that is associated with the adapter, only include the project name and not the project path.

    .
  10. Click Go.

    A new window opens, showing the scripts that are available in the specified project.

  11. Select the script to refer to by selecting the check box, and then click Finish.
  12. For functional testing scripts, supply the appropriate Script arguments.
    1. Click Script arguments.
    2. For Script Arguments, type the arguments to pass to the functional test script during execution.
    3. For Execution Arguments, type the arguments to go in the execution command line of the script, such as - classpath.
    4. If the script is associated with a datapool, in Datapool Iteration Count, type the number of iterations for the script to run.
  13. Click Save.
  14. To confirm that your test script is created, go to the main menu and click Construction > Browse > Test Scripts.
  15. Verify that the list includes your script.