Quality Assurance Planning
We start working on the quality assurance of the software product at the stage of developing requirements for it.
Test planning is a necessary process that includes:
- defining testing goals and strategies;
- labor cost estimation;
- resource allocation;
- risk assessment;
- risk elimination strategies development.
Test planning often starts with the development of a test plan. But if there is no such a document does, it doesn't mean that there is no planning.
A few years ago, we started planning testing of one large-scale project by developing a detailed test plan, taking standard templates as a basis. We spent a lot of time on detailed test plan creation and approval. De facto, we didn't use this document in the testing process but updated it frequently. A big document is a big problem.
We are confident that the test plan should help to optimize and control the process, not slow down and complicate it. We decided to replace a voluminous standard document with a simple, convenient one.
Now we have a universal template that is suitable both for large projects and for separate modules or small problems.
We describe testing goals and important organizational points in a thesis and then make a table that includes:
- functional area for testing;
- testing strategy;
- evaluation of labor costs;
- risk assessment;
- current status.
At present, we spend half the time to develop and update such a document.
The table is a visual and capacious tool with which we use it:
- We control the status of tasks in the process of testing;
- we manage the terms of task execution;
- analyze the accuracy of estimating labor costs, adjust it if necessary, and use it as an experience for estimating the following tasks;
- track priorities and update them.
Author: Kristina Sinugina, RHSoft QA Lead.