Talk about the "test plan"

 

 

Recently, through a requirement, I have a clear understanding and application of the test plan. The following are the main points of the entire test plan and the problems encountered in the test plan development process. Here are summarized and shared:

We often need to make plans in our daily life and work, just as the ancients have a cloud: everything is pre-established, but not pre-empted. This sentence fully illustrates the necessity and importance of the plan. The project has a project plan. Testing is a part of the project, and a test plan is also needed.

 

1. What is a test plan?

 

  1. The test plan is like writing a thesis, and the outline can be perfected step by step. With the test plan, you can master the progress and direction of the entire project. You can have a guiding role in the work without departing from the direction of the work.

  2. The test plan stipulates the expected goals, to what extent and within the expected time, such provisions can prepare the staff for psychological preparation, and the reasonable deadlines and goals can make the staff slack and complete the test tasks efficiently .

  3. As a plan for future work, the plan will definitely be subject to unexpected or unpredictable factors that will cause the entire project to be delayed or even impossible. Therefore, the necessity of risk assessment in the plan is to list the factors that affect the progress of the entire project, and formulate corresponding emergency plans to minimize losses.

  4. The development of the test plan is carried out after the completion of the demand analysis, so the execution of the test plan is also a further inspection of the demand analysis to a certain extent. If unreasonable factors are found during the formulation process, timely feedback can be carried out Adjustments will not cause many people to do useless work.

  5. The arrangement of the test plan is also a work guide for cooperation between multiple departments in a project, one link after another, and the handover of the work should be well detailed in time, so that the cooperation of the departments seems to be tacit.

 

Second, why should we develop a test plan?

 

  1. Formulating a test plan can directly transform one's own knowledge and experience into a specific method of performing tasks, in which the qualities and abilities of the formulator can be more reflected.

  2. Formulating a test plan can promote communication between teams about test tasks and processes, enhance the tacit understanding between teams, and can complete test tasks with high efficiency, high coordination, and high quality.

  3. Formulating a test plan can provide an overall framework for organizing, arranging, and managing test projects, analyze risks during project execution, and formulate relevant response strategies.

  4. Make reasonable arrangements for personnel in the test plan, and assign difficult tasks to each employee's expertise, the entire project will appear rational, hierarchical, and organized. At the same time, the responsibilities are clearly and clearly assigned to the individual, which is also conducive to future error correction. Even if any link is found to have a problem, it will be compensated in time.

 

3. When is the test plan developed?

 

       Under normal circumstances, after confirming the product requirements and doing test requirements analysis, we will start to write test plans. Of course, the work of writing a test plan needs to be determined according to the actual situation of the work, that is, specific analysis of the specific situation. Here is what the test plan needs:

  1. Test Scope: What is the test? The purpose of the test and a brief description of the project (purpose, background and scope).

  2. Test strategy: How to measure clearly? For different business needs, what test types, test scenarios and test methods are available.

  3. Resource arrangement: including the arrangement of testers, test environment, and test tools.

  4. Schedule: After clarifying the test scope, methods and personnel, we have to consider when to start the test and how long it is expected to be tested? In order to connect with the product launch plan.

  5. Confirmation letter that meets the upper limit conditions: it is to achieve the conditions that the test is completed and the product needs to meet, so that all roles in the project have a consensus goal.

  6. Risk remarks: Finally, we need to consider and prepare for the risks that may exist in the entire test process and the countermeasures when these risks occur in advance and retrograde, and reflect them in the test plan.

 

4. Problems encountered and solutions:

 

  1. The product thinks the test schedule is long, what should I do if the test schedule needs to be shortened? If the product reflects the simple demand function after seeing the test plan (simple demand function from the product level), the test time is too long and the test time needs to be shortened, then the whole process of the test must be described in detail, and if not What are the possible consequences of conducting a full test. In the end, if you decide to shorten the test schedule, you can call the product, development, and test to discuss the meeting, write down the meeting minutes and risks, and copy it to the three parties to prevent the occurrence of test lines that are not covered by the shortened test time. The problem occurred due to testing.

  2. How to write a test plan if the development does not mention all the functions or some functions are not scheduled? If, when writing the test plan, all or part of the functions are not tested or scheduled, an explanation is required, and the specific time will be written as to be determined. If the development is tested or given a schedule, it will be carried out Mail updates.

  3. What if some functional modules depend on other modules to go online for testing? At this time, you can make a note to explain the reason to be determined and to be evaluated.

       I hope the above questions about the test plan can help you, and everyone is welcome to communicate

 

 

Guess you like

Origin www.cnblogs.com/huile11/p/12738381.html