Adding existing test cases to test suites

You can add existing test cases to a test suite.


  1. Open an existing test suite or create one.
  2. Select the section Test Cases.
  3. Click the Add Test Cases icon Add.
  4. In the Add Test Cases window, select the test cases to add to the test suite.
    To refine the list of test cases, use column filters. To add more column filters, click the More icon Add Filter. For example, to list the test cases from a specific test plan, select a value for the field Test Plan and click Filter. All the test cases for the specified Test Plan are displayed.
    Note: To ensure continuity and accuracy between test artifacts and reports, if you include the test suite in a test plan, you must add test cases that belong to the same plan. If you do not include the test cases in the test plan, the test case result is still associated with the test plan that you select during test suite execution.

    If you have many test cases, you can use the Type Filter Text field to further refine the list.

  5. Click Add and close the window.
  6. Optional: You can select existing test cases in one browser instance and drag them onto the Test Cases section of a test suite in another browser instance.
    • For using the drag-and-drop method, make sure that both the source and target test artifacts are viewed in the instances of the same browser.
    • You can use the drag-and-drop method for test artifacts in the same project area only.
  7. To associate a test script to a test case or change an existing association, select the test case and click the Edit icon Edit in the Test Script column. Select the test script to associate.
  8. Optional: To associate an automation script in an external tool with a test suite in ETM, select the Run a test script option. Click the icon Add to open the Select a test script window. Select the test script and click OK.
    Note: Run a test script option is available when the property Use test scripts in test suites is enabled in the Manage Project Properties page. To enable the property, you must have the system administrative role. This option is applicable only for an automation test script.

    The script in the automation tool is not associated with test cases. Instead, the script is associated with the test suite in ETM and the test suite includes one or more test cases.

    When you add test cases to the test suite, the names of the test cases in ETM must match the names of the tests in the automation tool. For example, for an ETM test script of type JUnit Selenium, the names of the test cases must be same as the names of the test functions in the JUnit Script Class.

    When you run the test suite, it creates a result for all the test cases that have matching tests in the automation tool.
  9. Optional: To set the test environment for your test cases, select the test cases and click the Change Test Environment icon Bulk change in the Test Environment column. This step is necessary only if you want to override the test environment that is specified at the test suite execution record level.
  10. The order of the test cases is important if you want to run the suite in sequential mode. To change the order of the test cases in the list, select a test case to move. Click Move Up icon Move test case up or Move Down icon Move test case down in the action menu to change the sequence.
  11. Optional: To assign owners to test cases in the test suite, click the Change Execution Owner icon Bulk change in the Execution Owner column .
    The owner executes the test case in the context of the test suite. When you run a test suite, which has owners that are assigned to test cases, the test suite execution page shows the owner for each test case in the suite. As a tester, you can filter on the owner field to see the test cases in the test suite that you can execute.
  12. Save the changes to the test suite.


The test cases are added to the test suite.