Test Plan includes those aspects

Each part of the test plan:

Should the company have a goal in doing anything? Yes, the test plan itself is no exception. That is:Test Plan objectives
Of course, we want to test specific software. What is the background of this software? It is also composed of the main functional modules, which is an overview of the composition of the test plan.

With the overall understanding of the project, we went to the test planPart 2: Is the test created out of thin air? Of course not. It requires reference to many documents, that is, test reference documents.
,
Such as requirement documents, software testing requirements, summary design manuals, and user manuals. In addition to referring to the above documents, the test itself also produces many documents, that is, the test submission documents, such as the test plan, test cases, and defects.
Reports, use cases through statistical tables, test reports, and so on. Do not underestimate these documents. In fact, this part is very important to testers. This is generally referred to as the inputs and outputs of testers. When someone asks you
When the test outputs are: mainly those documents above, this is also yourWork


The embodiment of the results.

　　How can I manage the output documents? How do testers arrange their jobs? Can developers respond to tester requirements in a timely manner?

In fact, this is the third part of the test plan: Terms and definitions.
What terms should all have? 1) test case number. 2) test cases and document numbers. This is the basis for unified management of test documents. Time is very short. How should we arrange our work as a tester? We should test the priority according to 3. I found one.Bug


,
What is the harm to him? When is the most appropriate solution. Because developers are responsible for solving bugs. A unified language is required for communication. If developers use English and testers use Chinese
It will be a mess. Therefore, 4) the severity of the defect and 5) the priority of the defect is presented to developers. This should be agreed with developers. In this way, developers make appropriate decisions according to the requirements of testers.
Response.

Are we going to test the software's functions?

This is the object in our test. If the object is not clear, what kind of love do you want to talk about! (Haha) If this is not clear, what else can we use to write a plan. SoThe fourth part of the test plan is to test the specific functions of the test software, that is, the test content.

In fact, the fourth part of the test content solves what is or what to do. What we want to do below is how to do it. How can I perform a test? Of course, policies are required to solve any problem.The fifth part of software testing: testing strategy.
Test strategies should adopt different policies based on specific software, generally includingFunction Testing


, Interface testing, installation and uninstallation testing, usability testing, and so on.

I know what to do and how to do it. Then the question is who will do it.

　　Who will perform the test and what is the division of duties of testers?

This is Part 6 of the test plan.
Are you sure you want to perform the test? With a wooden board as a machete, of course not, who is doing it as a whole. What hardware and software environments do we need for testing tools. All should be proposed. That is, resources.

Now, it's all about what to test, how to test, and who to do the test. Is that all right? No. We are IT companies, high-tech enterprises, and high-tech enterprises need efficient management.Part 7 of software testing: Testing progress.
It mainly includes the assignment of test tasks. Assigned to a specific head. We also need to consider the time, so we should also include the resource requirements and schedule for each stage.Project Management


Li
Process management, that is, project milestones, must be required. At a certain time, we must make a small leap. In fact, there was a marathon who used to make the best use of this milestone. Their own Ratio
The competition routes are divided into small routes. For example, 1000 meters is a mileage, and He sprints in every 1000 meters. In this way, we have made a small leap, which eventually enables us to complete the big victory.

After the software is released, some modules you test have found many very serious bugs. This module is caused by time progress, project manager requirements, and limited resources. It has little to do with you, or has little to do with the test group. But when the problem occurs, do we have to wait for it?

No, IT professionals are all smart people. Just like we used to study the switch statement in C language, we considered various situations and finally had a default. Everything will think of unexpected situations, and this part is ours.Risk analysis should be taken into account in Part 8 of the test plan.

We canAll template documents used are placed at the end of the test plan as an appendix.
. Main template: TestLogs


, Routine record, test cases, test summary, and so on.

The above is the nine parts of the general test plan. Do you remember?