The test time is not enough and the project should be released as scheduled. How to ensure the quality of the test

Quality Assurance Program

Find the project leader to confirm

1. Set the test priority and test strategy, that is, which functions are to be tested first, are the main processes and interface styles guaranteed, and other branch processes and details can be left for later test optimization?
2. Does the bug only ensure that the bugs above the severity level are completely repaired, and the others are repaired as much as possible, and can't be left to be resolved in subsequent versions?
3. Can personnel be borrowed, such as pulling up products and running tests together?
4. Coordinate the extremely helpless overtime plan, and leave time for the test as much as possible.

Communicate with the product group

Let the corresponding product and development meet together, the product will explain in depth the needs of this iteration, the development explanation and the points of attention, to ensure that the three parties, especially the testing personnel, quickly understand the needs and save time

Analyze the causes and take preventive measures

1. The time when the superior is dead

Insufficient preliminary time assessment;
superiors shoot their heads to determine the dead time;
seize the market, rush to product launch conferences, etc.
Don't let abnormalities become the norm. Give feedback to the leaders: Although the product is online this time, there are many hidden dangers in the actual product, and it is necessary to arrange time to deal with it in a timely manner.

2. Inaccurate assessment

Insufficient early-stage evaluation, and the technical difficulty far exceeds expectations;
facing the first reason, let the development learn lessons later, and do a good job of risk and problem assessment;

3. The requirement setting design is incomplete and changes too much

The incomplete design of the requirements in the early stage leads to frequent changes in the future ;
because of the continuous feedback from customers, testing, and development, the product directly adds the requirements;
feedback to the project leader: if it is not necessary in the future, it is necessary to prevent the requirements from being reviewed and approved before making changes , As much as possible to arrange the new demand to the next period; even if it is modified, it is necessary to do a good assessment of the demand change, weigh the workload and necessity before making a decision.

4. The quality of the development self-test is not good

Have a good talk with the person in charge of the project and the person in charge of development, and let the development strengthen the function self-test and improve the quality of the test.

Guess you like

Origin blog.csdn.net/aaaaaaaaanjjj/article/details/115299935