What Was Improved in Spira Version 5.0+
In the major rewrite for SpiraTest and SpiraTeam we updated how the test set folders work. We rewrote all of the database code to improve performance and added cached counts to all of the test sets, test set folders and the summary counts for test sets and test set folders for each release/iteration in the system.
The result of this is that you can now:
- View the list of test sets by folder for 'All Releases' and see the count/status for the test sets
- View the aggregated count of this information for the different levels of test set folders for 'All Releases'
- View the list of test sets by folder for a specific release/iteration and see the count/status for the test sets
- View the aggregated count of this information for the different levels of test set folders for a specific release/iteration.
What Side Effects Are There?
However as part of the change, to provide high performance, when you filter the execution status of the test sets by Release or Iteration (i.e. you have the Display Data For = Release X), the system does the following:
- If you have a test set that contains 5 test cases that are all not run; when you view the list of test sets in the Testing > Test Sets page, it will show the test set execution status of '5 test case(s) not run'
- If you have a test set that contains 1 test case that is passed, and 4 test cases that are all not run; when you view the list of test sets in the Testing > Test Sets page, it will show the test set execution status of '1 test case(s) passed and 0 not run'. When you switch back to 'All Releases' it will show '1 test case(s) passed and 4 not run'.
How Does this Affect Reports?
When you run the test set summary and test set detailed report with a Release filter, Spira will do these two things:
- It will filter the list of test sets by the specified release (this is equivalent to filtering by that column on Test Set List)
- It will also apply the Display Data For = Release X setting for the same release.