Skip Navigation LinksForums > SpiraTeam Forums > SpiraTeam Best Practices > How to group test cases f...

How to group test cases for multiple runs (multiple test cycles) RSS Feed

Friday, April 24, 2015
What is the best out-of-the-box way of grouping test cases together for multiple test runs (aka cycles)?

It looks like test cases can be assigned to a release or iteration, or test cases can be assigned to a test set.

What's Inflectra's vision for how this is done?

I would like to be able to look at my release page and the column Test Coverage and quickly see how many tests have been passed, failed, cautioned, blocked, and not run.  

If I have multiple iterations in a release, each for a different and parallel set of functionality, should each each of those iterations have one child iteration per test cycle/run for the parent iteration?  That would seem to provide us with the view we want.  (It doesn't necessarily use Test Sets at all, for better or worse.)

1 Replies
Jim R.Jim R.
re: Jon Freed on Friday, April 24, 2015
Tuesday, May 5, 2015
Hi Jon

There are two main options:
  1. Using the Iterations for this, so that each 'cycle' is an iteration in each release
  2. Using the test sets, create a test set folder for the release and then each test set under the folder could be a 'cycle'.


  • Started: 4/24/2015
  • Last Reply: 5/5/2015
  • Replies: 1
  • Views: 8859
Powered by KronoDesk v1.1.0.15 | © Copyright Inflectra Corporation 2011-2017 | Licensed to Inflectra Corporation.