QA Process Mapping On Test Rail

There is a lot of Buzz around TestRail test management system owing to its efficiency in managing releases, test cases & test results. TestRail also makes it easy to track individual tests, milestones, and projects with its Dashboard and activity reports. What this does is; it helps to manage and track software testing efforts as well as organize large sets of test cases which makes it an efficient QA management tool.

Below is an attempt to map the QA process in the TestRail management system.

Mapping QA Process to TestRail –

Let us consider a typical QA process where a new build is released for testing, plan, and test cases are created, execution is done on test environments, test results are updated and a summary/quality report is sent at the end of the test cycle. Given below are the steps to map this process in Test Rail –

Step 1: A new test build is released for each release, with few new features and bug fixes implemented

Action on TestRail: Create a Milestone with release name. Say Release 1.2.1.

Step 2: A high-level plan is created with the strategy, schedule, and deliverables

Action on TestRail: No Change on Test Rail

Step 3: Test cases are created for the new implementations in the release (Features & Bugfixes)

Action on TestRail: Test cases can be organized in folders called ‘Test Suites’. Test cases on new features can be added to respective Test Suites.

Step 4: Test cases are executed on pre-defined environments for new features and bug fixes are retested.

Action on TestRail:
Add a test plan with build name say Build, and associate with the milestone 1.2.1. Add two test runs with names say ‘Release test cases’, ‘Regression test cases’, add respective test cases to these runs as the name indicates. Add a couple of environments as configurations to each test run.

Step 5: Test results are updated; bugs are followed up until fixed.

Action on TestRail:
Open each test cases to be executed, click on ‘Start Progress’ and execute the test case. When execution is completed click on the ‘stop’ button.

Step 6: Quality report sent with outstanding bugs, ZenQ’s recommendation on build readiness to release.

Action on TestRail:
Reports can be generated as defined in the ‘Reports’ section

Below reports can be generated in Test Rail –

By following the above steps on TestRail, a QA manager can effectively and efficiently manage and track test cases.