This page is maintained for older versions of Spira only. The latest documentation can be found at: https://spiradoc.inflectra.com

Spira 4.2 User Manual Help Viewer

1. Introduction
2. Functionality Overview
3. User/Project Management
4. Requirements Management
5. Test Case Management
6. Incident Tracking
7. Release Management
8. Task Tracking
9. Resource Tracking
10. Document Management
11. Reports Center
12. Source Code
13. Planning Board
14. Mobile Access
Search:
1. Introduction
2. Functionality Overview
3. User/Project Management
4. Requirements Management
5. Test Case Management
6. Incident Tracking
7. Release Management
8. Task Tracking
9. Resource Tracking
10. Document Management
11. Reports Center
12. Source Code
13. Planning Board
14. Mobile Access

5.7. Test Set List

As well as being able to organize test cases into folders, you can also create separate groupings of test cases called test sets which can then be assigned to testers as a package. To view the list of test sets for a project, click on Testing > Test Sets in the global navigation:

The test set list consists of hierarchical list of all the test sets in the current project organized into folders. When you create a new project, this list will initially be empty, and you will have to use the <Insert> button to start adding test sets to the system.

Each test set is listed along with the number of test cases contained (in parenthesis), the aggregate execution status of the contained test cases (using a graphical bar-chart), the date that the test set has been scheduled to be executed (planned date), the date that it was last executed, the person currently assigned to execute the test set, the status and the test set id. Clicking on a test set’s hyperlink will take you to the test set details page for the item in question.

Note: the test set status is separate from the execution status of the individual test cases and represents where the test set is in its lifecycle:

  • Not Started – The test set has been assigned to a tester or automation host and no testing has been performed.
  • In Progress – The test set has been assigned to a tester or automation host and the testing is in progress.
  • Completed – The test set was previously assigned, but has now been completed, with all test cases having an execution status recorded and the tester having clicked the Finish button in the test execution wizard.
  • Blocked – The tester or automation host was unable to execute the assigned test set because of a failure external to the actual test case.
  • Deferred – The test set was previously assigned, but was execution was paused by the Tester clicking the [Pause] button during test execution and the Pending Test Run entry was deleted from the user’s My Page.