is a detailed document that describes which test strategy will be used, which schedule, estimation, which resources required for testing.
It is the base for formally testing any software/product in a project.
There are the following steps for creating a test plan as per IEEE 829:
Need to gather as much information about the product as possible to understand it better, what it's features and functionalities. It should be a good understanding of user requirements and expectations.
It is a critical step. Should be defined:
the project’s testing objectives and the means to achieve them
testing effort and costs
The goal of any software project is to release a high-quality bug-free software product. It's good to clearly define the testing scope and its boundaries. For this step useful to do the following steps:
make a list of all the software features which may need testing
select the testing targets based on features listed previously
Rule on which a test procedure or test judgment can be based. There are 2 types of test criteria:
Suspension Criteria
Exit Criteria
Should be planned a detailed summary of all types of resources required to complete the project task. It can include: This important step helps to determine the number of resources that will be used for the project.
Test Environment is a place where the testing team is going to execute test cases. Consists of real business and user environment, as well as physical environments, such as server, front end running environment.
The developed schedule helps to control the progress of the testing process. Should be considered the following factors like:
Project estimate
Project risk estimate
Resource estimate
Employee roles & responsibilities
Test activity deadlines
The last step is to prepare a detailed test deliverables document as the list of all the documents, tools, and other components that have to be developed and maintained in support of the testing effort.