Join 34,000+ subscribers and receive articles from our blog about software quality, testing, QA and security.
 

How to achieve release wise status by maintaining individual suites


#1

Hi

We are having the project with 4 main modules and each main module is having sub modules… as below.

Module-1:
Sub module-1
Sub module-2
Sub module-3
Module-2:
Sub module-1
Sub module-2
Sub module-3
Module-3:
Sub module-1
Sub module-2
Sub module-3
Module-4:
Sub module-1
Sub module-2
Sub module-3
Now our requirement is that we are working on Release -1 for this release we need to maintain individual suits for each module and we are try to use baseline to track the status of Release-1 and for upcoming releases.

How can we achieve this, If yes please give us steps to achieve this.

Thanks,
Raj Kumar.


#2

Hi Raj,

Thank you for the post. Bif you have to maintain multiple major project versions for a long time in parallel. That is, your team needs to maintain and release multiple main branches (e.g. 1.x and 2.x) in parallel for many months or years, and the test case details will be quite different for each baseline over time, as each version will need different test cases. From your description, it sounds like this may be the case with your testing. I would recommend taking a look at the following blog post as it discusses baselines and their purpose.

https://blog.gurock.com/test-management-test-case-versioning/

You may also want to look into using milestones to separate your testing efforts as well. These add an extra layer of separation to your releases that helps you maintain different sets of tests.

http://docs.gurock.com/testrail-userguide/userguide-gettingstarted#projects_and_milestones


#3

Hi Martylavender,

Thanks for reply, Actually this information very much helpful for managing test cases, but we need more information about how to maintain individual test suites for each module for baseline as mentioned below.

Relese 1.1
Test Plan
Test Suite for module 1
Test Cases for module 1
Test Suite for module 2
Test Cases for module 2
Test Suite for module 3
Test Cases for module 3
Test Suite for module 4
Test Cases for module 4

Actually we are trying to categorize test cases in suites itself.

How can we achieve this, If yes please give us steps.

Thanks,
Raj Kumar.


#4

Hi Raja,

Thanks for your reply! With TestRail’s Baselines project mode, each baseline would represent a separate release version, and each baseline is considered a ‘test suite’ in TestRail. Inside each baseline/suite, you would add your Modules and Submodules using TestRail’s sections and subsections. You can also use Milestones to help organize your test execution, and many teams would use milestones to represent their sprints/releases. You can then create test plans to group together related test runs if needed, and when creating these you would be able to add multiple test suites/baselines to your test plan as needed (and these would already include your modules/submodules as they are inside your baselines). So this would be handled automatically when creating test plans, and you can link the plan to an overall milestone/release version if needed. Hope this helps to clarify this!

Regards,
Marco