Manage Test Sets

Print this topicEmail this topicSave as PDF

What is a Test Set?

Test Sets allow you to group and schedule regression tests in an iteration or release. For example, a test set could include smoke, configuration, system, etc. tests. Once grouped, the test cases can be run together.

Test Set consists of the following topics:

Creating a Test Set

A test set is a container for test cases which can be run in an iteration or release. You may create a test set from any of the three page types:

From the iteration or release status page:

  • Iteration Task Status: Click
  • Iteration Test Status: Click
  • Iteration Defect Status: Click

To schedule a test set:

  1. Choose the Schedule New Test Set... from the Actions menu.
  2. Enter information in the test set editor then Save.
  3. The test set now displays in the status view.

Adding Test Cases to a Test Set

Test sets are containers for test cases. After the test set has been created, test cases must be added to the test sets. Adding test cases to test sets is only available on the Iteration Test Status page.

From the Iteration or Release status page:

Iteration Test Status: Click

To add Test Cases to an existing Test Set:

  1. From the iteration test status page click the Add Test Cases icon.
  2. The test case chooser displays. Select the test cases(s) you want to add to the test set.
    • Use the Project drop down to display test cases from a different project.
    • Use the sort and filter options to narrow your list of test cases in the view.
    • If test cases are organized in test folders, use the Test Folder filter to view only those test cases then add them to your test set.
  3. When saved, the test case is automatically associated with the test set.
  4. Expand the test set to view all the associated test cases.

Editing a Test Set

You can edit a test set. Edit is available from any of the three page types:

From the Iteration or Release status page:

  • Iteration Task Status: Click
  • Iteration Test Status: Click
  • Iteration Defect Status: Click

With the Editor:

  1. Click the edit icon Inline Edit of the test set you want to edit. The editor displays.
  2. Complete your edits.
  3. Choose Save & Close, Save & New, or Save.

Inline:

  1. Double click the test set row you want to edit. The row changes to edit mode.
  2. Complete your edits.
  3. Click Inline Save to save your defect or click Cancel to cancel.

Copying a Test Set

Save time and effort by copying an existing test set then editing the copy to make necessary adjustments. You can copy a test set from any iteration or release status page. Copy is available from any of the three page types:

From the Iteration or Release status page:

  • Iteration Task Status: Click
  • Iteration Test Status: Click
  • Iteration Defect Status: Click

To copy a test set:

  1. Click the copy icon of the test set you want to copy. The editor displays.
  2. Complete your edits. Update the change the iteration and/or release fields to reschedule the test set.
  3. Choose Save & Close, Save & New, or Save.
  4. The test set and all related test cases are copied.

Running a Test Set

When you create and populate test sets, you can easily execute test cases contained within a test set from a single location. Running a test set is only available on the Iteration Test Status page.

From the Iteration or Release status page:

Iteration Test Status: Click

To run a test set:

  1. From the iteration test status page, click the Run icon of the test set you want to execute test cases.
  2. The test run page displays all test cases and their related test steps contained within the Test Set. Use this page to run each test case within the test set.
  3. From the test run page, test case results and defects can be created and the test case can be edited by clicking the appropriate icons.
  4. The test set status rollup bar displays at the top of the page. The status bar reflects the state (pass, fail, inconclusive, other) of the test cases in the Test Run. Hover over the test set status display to view the percentage and number of Test Cases in each state.

Deleting a Test Set

You can delete an entire test set. Delete is available from any of the three page types:

From the Iteration or Release status page:

  • Iteration Task Status: Click
  • Iteration Test Status: Click
  • Iteration Defect Status: Click

To delete a Test Set:

  1. Click the delete icon of the test set you want to delete.
  2. A message appears asking you to confirm the delete.
  3. Click OK to confirm your action and the test set is deleted.

Deleting a test set does not delete the test cases or test case results. The association between the test set and test cases is removed.

Remove a Test Case from a Test Set

Test cases can be removed from a test set. Removing a test case from a test set is only available on the Iteration Test Status page.

From the Iteration or Release status page:

Iteration Test Status: Click

To remove a test case from test set:

  1. Expand the test set to display the associated test cases.
  2. Click the remove test case icon of the test case you want to remove.
  3. A message appears asking you to confirm.
  4. Click OK to confirm your action and the test case is removed from the test set.

Test Set Fields

The following fields are presented to help you describe or add detail to a test set. These field values can be set when creating or editing a test set.

Required fields are highlighted in red on the full screen editor.

Field Description
General
ID A system generated ID that is assigned to your defect suite; it is unique and will never change. The ID consists of a tag prefix and a numerical value. The tag can be customized by your system administrator to reflect a differentiating prefix for each work item defined in your project.
Name A textual Name of the defect suite.
Description Use this rich text format field to record a description of the defect suite.
Owner Specify the owner of the defect suite.
Project Select a project from the drop down list.
Schedule
Schedule State Indicates the progress that has been made toward the completion of the defect suite. There are six states that can be set from the drop-down list. The first and last states can be customized by your subscription administrator to help you better manage your process. The following identifies the default states that the defect state can move through:
  • Defined: The development team can write tasks and provide estimates. This is the defaulted state value for a new defect suite and cannot be customized.
  • In Progress: The defect suite has been committed to an iteration and work has begun. This state can not be customized.
  • Completed: All related tasks have been completed. When the state for all of the tasks are set to Completed, the defect suite is automatically rolled up to reflect the Completed state regardless of its initial setting. This state can not be customized.
  • Accepted: The acceptance criteria has been met. This state can not be customized.
Blocked Indicates that work on the defect suite can not continue until all issues preventing further progress are removed. If a task has been marked blocked, this field will automatically be checked in the editor. You can also manually block the defect by editing it and activating the checkbox. The blocked state will appear in the iteration status or release status view in red to indicate blocked, but will still carry the associated state letter so the initial state of the defect suite is not lost.
Release/Iteration These fields indicate the release or iteration to which the defect suite is assigned. Select a release or iteration by clicking the drop-down to list of all available releases or iterations contained in the project.
Plan Estimate Use this field to record how much effort is estimated to complete the defect. This field is a real number and can accept three digits followed by a decimal and two more digits. The units are defined by your administrator.
© 2012 Rally Software Development Corp | Legal