Creating test suite execution records

You can manually create a test suite execution record. Test suite execution records specify the execution environments for an instance of a test suite, run a test suite instance, and track the status of each test run.

Procedure

  1. From the main menu, click Construction, and in the Create section, click Test Suite Execution Record.

    The Create Test Suite Execution Record page opens.

  2. On the page, type a name for the new test suite execution record.
  3. If team areas are enabled for the project area, select a team area from the list.
    Remember: Team areas can be enabled only from the Manage Project Properties page.
  4. Select an owner from the list.
    Typically, the owner is the person who is responsible for running the test suite.
  5. Type a description of the test suite execution record.
  6. Complete the Overview section.
    1. To associate a test plan with the test suite execution record, click the Select Test Plan icon (Add). If you select a test plan, the Iteration field is populated with information from the associated test plan.
    2. Required: To assign the test suite execution record to a test suite, click the Select Test Suite icon Add.
      Important: A test suite execution record must be assigned to a test suite. If you selected a test plan for the test suite execution record, only the test suites that are associated with that test plan are included in the list.
      After you select a test suite, these fields are automatically populated with values from the associated test suite: Available Test Environments, Priority, Weight, and Estimate. You can edit those values.
    3. Select the iteration to assign the test suite execution record to.
      Test iterations are defined in the Test Schedule section of the test plan. If you assigned the test suite execution record to a test plan, the test iterations are available only in the Test Schedule section.
    4. From the Available Test Environments list, select a test environment that defines the runtime environment.
      A test environment is a set of saved attributes; for example, a particular browser, operating system, hardware platform, and other attributes for a particular computer.

      By default, the test environment that you specify at the test suite execution record level is used for all test cases that are run as part of the suite. To use a different test environment for a test case in a test suite, specify a new environment in the Test Cases section of the test suite.

    5. Define categories.

      You can use categories to define a hierarchical organization of test plans, test cases, test scripts, and other test artifacts. You can also define subcategories and other category relationships. You can use the default categories that are provided or create your own. To define categories, click the Manage Test Suite Execution Record Categories icon Manage category.

    6. Assign values to the custom attribute fields.
      If an administrator defined any custom attributes for test suite execution records, the attributes are shown in the Attributes section of the Summary. The field values for custom attributes can be in text, integer, or date format. You can sort or filter your test cases by using custom attributes in the same way that you use categories.
  7. Click Save.
    By default, when a test suite execution record is created, test case execution records are created. You can change that behavior in the Execution Preferences section of the Manage Project Properties page.

What to do next

After you run the test suite, you can record the time that was required to complete it in the Time Spent field. You can use that information to improve your estimates of the time that is required for future test runs and to track the time that you invest in testing.

You can also subscribe yourself and other team members to receive email notifications for the changes that occur to the test suite execution record. For more information, see Receiving email notifications for changes to test artifacts.