Test sets are a collection of test cases (optionally stored in test folders.) Test sets allow you to group and schedule regression tests into iterations or releases. Test sets are only created and used on the Iteration and Release Status pages. You can also copy test sets from one
to another. A test set could include smoke, configuration, system, and so on. Once you group them, you can run test cases together.
To learn more about test sets and the concepts behind quality management, select here.
Managing test sets includes the following:
View a Test Set
The Test Set QDP shows the Tasks, Test Cases, and Discussions collections for the test set. Select a collection to display the collection items in the left panel.
The remaining test set fields can be viewed in the QDP panel.
Create a Test Set
A test set is a container for test cases which can be run in an iteration or release.
- In the QDP, complete the fields as necessary.
- Select Create.
The test set displays at the bottom of the summary page.
Add Test Cases to a Test Set
Add test cases to test sets inline on the Iteration Status page.
- From the Iteration Status page, select the row action icon on the test set and select Add Child Inline from the drop-down menu.
- The Child Type automatically defaults to Test Case. Enter the Name, Type and Method fields.
- Select Create+New to add the test case and create another test case, Create to add the test case to the test set, Add Details to enter additional test case details, or +Add Existing to add a test case that has already been created.
- You can expand the test set to view all associated test cases by selecting the arrow next to the test set.
Edit a Test Set
With the Editor
- From the Release summary page, select the edit icon of the test set you want to edit. From the Iteration Status page, select the FormattedID of the test set you want to edit, or select the row action icon next to the test set and select Edit from the drop-down menu.
- In the QDP, complete your edits as necessary.
- Select Save.
- From the Release summary page, double-click the test set row you want to edit. From the Iteration Status page, you can edit inline with a single select.
- With the row in edit mode, complete your edits.
- Inline edits are saved automatically when you select away from a field or tab to the next field.
Re-Order Test Cases in a Test Set
Rank test cases within a test set by using
. To change the order of a test case, select the test case and drag it to the correct placement.
If your workspace is set to use manual ranking, you can change the order or priority of a test case by double-clicking on the case and entering a rank value.
Copy 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 the Iteration or Release Status page.
- From the Release Status summary page, select the Copy icon of the test set you want to copy. From the Iteration Status page, select the row action icon next to the test set you want to copy, then select Copy.
- Select the FormattedID to open the copy for editing in the QDP.
- Complete your edits.
- Select Save.
Run 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 Status page.
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.
- From the Iteration Status page, select the row action icon next to the test set and select Run Test Set.
- From the Test Run page, you can create and edit test case results and defects.
The test set status roll-up bar displays at the top of the page. The status bar reflects the
(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.
Delete a Test Set
You can delete an entire test set.
- On the Iteration Status page, select the row action icon next to the test set you want to delete and select Delete from the drop-down menu.
- Select OK on the confirmation message.
Deleting a test set does not delete the test cases or test case results. Only the association between the test set and test cases is removed.
Remove a Test Case From a Test Set
You can remove test cases from a test set. Removing a test case from a test set is only available on the Iteration Status page.
- On the Iteration Status page, expand the test set to display the associated test cases.
- Select the row action icon next to the test case you want to delete and select Remove from the drop-down menu.
- Select OK on the confirmation message.
Test Set Fields
The following fields are available to help you describe or add detail to a test set. Set these field values when creating or editing a test set.
Required fields are indicated by an asterisk (*).
||A system-generated ID that is assigned to your test set; it is unique and will never change. The ID consists of a prefix and a numerical value. The prefix can be customized by your system administrator for each work item type in your workspace.
||Enter a textual name of the test set.
||Specify the owner of the test set.
||This state can be used to indicate that a test set is ready to be worked. This field is primarily used by teams using the Kanban Board or other board based method of pulling work.
||Select if work on the test set cannot 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 test set by editing it and selecting Blocked. The blocked state displays in the Iteration Status or Release Status page in red to indicate blocked, but will still carry the associated state letter so the initial state of the test set is not lost.
If the test set is blocked, use the text field to enter a reason why it is blocked.
||Specify the progress that has been made toward the completion of the test set. There are six states in the drop-down list. The first and last states can be customized by your subscription administrator to help you better manage your process. The default states that the test set can move through are:
- Defined: The development team can write tasks and provide estimates. This is the defaulted state value for a new test set and cannot be customized.
- In Progress: The test set 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 test set is automatically rolled up to reflect the Completed state regardless of its initial setting. This state can not be customized.
- Accepted: The
has been met. This state can not be customized.
||Record how much effort is estimated to complete the test set. 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.
||Select a release or iteration from the drop-down which lists all available releases or iterations contained in the project.
||Add milestones to track progress towards deliveries and deadlines.