We had a customer looking for a consolidated report of the test sets and their test cases, grouped by release and test set folder. The report needed to have the individual test case instances in the test set along with the associated test runs.
We had a customer that was looking for a more automated way to remove test cases from a test set. The good news is that our REST API makes this easy.
This article explains what to do if you are attempting to execute a test set and get this error message: "There are no test runs in this pending set to be resumed."
Sometimes customers will contact us regarding questions as to why the execution status indicator of their test sets is not being updated (i.e. everything still looks as not run) even after running some of the test cases. This article explains why this might be the case and provides solutions.
Sometimes you want to test a process which requires a handoff between departments and would involve different testers to complete the full range of functionality. This article describes how to set that up, using a test set.
One of the limitations in SpiraTest and SpiraTeam v4.x was that for performance reasons we could not handle test sets with very large numbers of test cases and that the system was not able to display the counts of the test cases and the execution status for test set folders.