Baseline supporting project template won’t work for us.
Maybe you can help me to figure out the best way for us to set up the system:
- At the beginning of each iteration (be it a sprint, a release, etc.) we create our release specific test cases.
- For some of these test cases there will be separate regression tests after the release, others will be abandoned.
- In addition to these test cases we run regression tests while we are coming closer to the release date.
- There are daily automated tests, too, which we are planning to add to the TestRail database.
This is what I thought:
Regression tests should go to one or more test suites organised by topic.
Feature tests should go to one test suite for each release, (e.g. Features Release 1.0, Features Release 2.0, etc.)
Automation tests are organised in one or more test suites by topic.
My problem is, that since I cannot close test suites, the list of suites is getting confusingly long. Do you have any suggestions?
Adding a [closed] string is just a workaround for a feature which I consider mandatory in a test case management system that claims to support multiple test suites.
Thanks in anticipation.