Master Test Suite

Overview:

Master Test Suite is an efficient and repeatable testing process that avoids fragmentation & duplication of testing efforts and streamlines the QA workflow. It supports individual projects with standard releases, as well as more complex areas where there is a superset of various Test Suites across different projects that are testing the same underlying released system. By planning and executing across the Master Test Suite we can confidently certify the overall release candidate. During each release testing, we select a targeted scope and prepare the execution suite based on the requirements (user stories) in the scope of the release. By ensuring test cases are mapped to the requirements they cover, test selection becomes automatic, and traceability is achieved. The structure of the Master suite is based on the features of the application – not based on the team structure, Jira ticket IDs, or calendar/dates.

MTS Practices:

The Master Test Suite approach recommends various testing best practices listed below:

All the testing activities, including the release testing activities, are managed by a single test management tool [eg: qTest]
The testing process for in-sprint testing In-Sprint Test Process
The testing process for release testing Release Testing Process
Requirements How Do I? - Requirements | Organize the Requirements
- The requirements shall be imported from Jira and maintained in qTest
- Test cases are always mapped to the requirement(s) they cover
Test Design How Do I? - Test Cases | Create A New Test Case
- Test cases are organized according to the features and applications
- Test cases use a standard test case template with required fields
- The test cases are mapped to the requirements
Test Execution How Do I? - Test Selection & Execution | Create an RTS for Release Regression
- The test sets are created from the requirements
- Test executions are performed against the release
Insights QA Test Execution Summary Report - Master Test Suite - Example Release
- Quality Analysis is configured for a given release
- Coverage Analysis is configured for a given release
- The required metrics are tracked through Insights

Quick Links

Risk Based Testing Unit Testing End User Experience Testing ART Regression

Practice	MVP	MVP +
Unified test management tool	+
In-sprint testing process	+
Release testing process	+
Requirement, Test Case, Defect Traceability	+
Feature Based Test Case organization	+
Unified Test Case template		+
Requirements driven testing		+
Quality Analysis Report		+
Coverage Analysis Report		+
Metrics Tracking		+

Roles

Name	Responsibilities
Product Owner Scrum Master/Team Coach Business Analyst	Help define/refine the feature set for applications
QA Specialist (Functional SME)	Help define/refine the feature set for applications, and maintain the feature structure in qTest Follow MTS approach for test case authoring, maintenance, and execution
ART Release Quality Manager (RQM)	Ensure MTS process is followed by teams, and drive release testing MTS process

Name

Responsibilities

Product Owner
Scrum Master/Team Coach
Business Analyst

Help define/refine the feature set for applications

QA Specialist (Functional SME)

Help define/refine the feature set for applications, and maintain the feature structure in qTest

Follow MTS approach for test case authoring, maintenance, and execution

ART Release Quality Manager (RQM)

Ensure MTS process is followed by teams, and drive release testing MTS process

Tools

Functionality	Tool Name
Test case management tool	qTest
User Story management tool (for Requirements to flow into qTest, and test executions to be visible on the stories they cover)	JIRA