Welcome to the Manual Testing Free Training series.
In the last tutorial, we talked about the test plan documents. Please refer to the following link:
Read Test plan document
Master Test Plan
The master test plan is a document that defines how the testing is being projected and how it will be handled across different test levels. It gives an overview of the key decisions taken, the strategies to be implemented, and the testing efforts included in the project.
Details provided by Master Test Plan
In simple words, the master test plan for software testing provides the following details:
- List of tests to be executed.
- Testing levels to be assured.
- Relationship between different test levels and related coding activity.
- Test execution strategy.
- Justify testing effort, which is a section of the project.
- The master test plan should adjust with test policy and test strategy and list out all exceptions or errors and their possible impact.
Example – If regression testing is always mandatory before the release of a product, but no regression testing is needed before the release of a product. That information should be in the master plan document with justification, and it also points out the impact of skipping regression testing, if any. Besides, It should also list out the steps taken to lessen any risks that occur from skipping regression testing.
Also read Test Plan and Test case
The structure of the master test plan and its content depends on the following factors:
- Type of organization
- Documentation rules followed by the organization
- Level of project formality
Content of Master Test Plan
A master test plan should include the following points:
- List of items to be tested.
- List of items not to be tested.
- List of product quality features that will be tested.
- List of product quality features that will not be counted for testing.
- Test execution cycles.
- Test budgets according to the project or overall operational budget.
- Testing schedule.
- Interaction between testing cycles and release plan.
- Interaction between other departments and the testing team.
- Scope of each test item.
- Predefined entry, continuation, and exit conditions for each test level.
- Risks associated with the test project.
- Management and control of testing.
- Team members are responsible for each test level.
- Inputs and outputs for each test level.
Level Test Plans
As the name suggests, a level test plan describes in detail the testing activities that must be carried out for every test level or, sometimes, test type. Normally, the test levels listed in the master testing plan are explained in the level test plan.
They should provide the testing schedule, targets, test activities, test templates, etc., which are not mentioned in the master plan.
For Instructor-led training
For Self-Driven training
So, in short, a Master Test plan is a high-level test plan for a project/product that joins all other test plans, on the other hand, Testing levels are specific like a Unit Test plan or Integration Test plan.
In the next tutorial, we will dig into System testing, plan, and others.
Happy learning, until then.