Let’s Write A Test Plan
Test plan is a detailed document that describes the test strategy, objectives, schedule, estimation, deliverables, and resources required to perform testing for a software product. This test Plan helps us to determine the effort which is needed to validate the quality of the application under test. This article will explain, how to write a proper test plan which is minutely monitored and controlled by the test manager.
The planning test is the most important part of the testing because it clearly shows all the important steps which should be followed step by step like a guidebook. So, before writing a test plan there are some important steps to be considered.
- Analyze the product
This step is referred to learn the product thoroughly before testing it. When learning the product you should focus on,
- Who will use the website?
- What is it used for?
- How will it work?
- What are software/ hardware the product uses?
To fulfill these objectives, you can have interviews with the client, designer, and developer, review product and project documentation, etc.
2. Design a test strategy
Test Strategy is a critical step in making a Test Plan in Software Testing. A Test Strategy document, is a high-level document, which is usually developed by Test Manager. This document defines, the project’s testing objectives and the means to achieve them, and determines testing effort and costs.
To build up a test strategy, you have to follow below steps.
- Define scope of testing
- Identify testing type
- Document risks and issues
- Create test logistics
3. Define the test objectives
Test Objective is the overall goal and achievement of the test execution. The objective of the testing is finding as many software defects as possible, to ensure that the software under test is bug free before release.
To define the test objectives, you should do 2 following steps
- List all the software features (functionality, performance, GUI…) which may need to test.
- Define the target or the goal of the test based on above features
4. Define test criteria
Test Criteria is a standard or rule on which a test procedure or test judgment can be based. There are 2 types of test criteria as suspension criteria and exit criteria.
Suspension criteria specifies the critical suspension criteria for a test. If the suspension criteria are met during testing, the active test cycle will be suspended until the criteria are resolved.
Exit criteria specifies the criteria that denote a successful completion of a test phase. The exit criteria are the targeted results of the test and are necessary before proceeding to the next phase of development.
5. Resource planning
Resource plan is a detailed summary of all types of resources required to complete project task. Resource could be human, equipment and materials needed to complete a project.
6. Plan test environment
A testing environment is a setup of software and hardware on which the testing team is going to execute test cases. The test environment consists of real business and user environment, as well as physical environments, such as server, front end running environment.
7. Schedule & estimation
In the Test Estimation phase, you are supposed to break out the whole project into small tasks and add the estimation for each task. After completing it, you should create the schedule to complete these tasks.
Making schedule is a common term in project management. By creating a solid schedule in the Test Planning, the Test Manager can use it as tool for monitoring the project progress, control the cost overruns.
To create the project schedule, the Test Manager needs several types of input as below:
- Employee and project deadline
- Project estimation
- Project Risk
8. Determine test deliverables
Test Deliverables is a list of all the documents, tools and other components that has to be developed and maintained in support of the testing effort. There are different test deliverables at every phase of the software development lifecycle such as before testing, during testing, and after testing.
