What is defect analysis?An article takes you to understand the necessary skills of test engineers

Defect analysis is also a skill that test engineers need to master, but many times people only remember to submit defects and count defects, but ignore defect analysis.

In fact, the defect records of each project are of great value.In the testing phase, analyze the current defect situation, find out the existing problems in time and adjust the testing strategy, so as to reduce the risk and loss.After the test, it is also necessary to summarize through the defect analysis, continue to carry forward the good parts, and reflect and correct the bad parts in time.

Many students will wonder, if you want to analyze, where to start?Here are a few starting points for defect analysis:

1. Overall Defect Trend

The normal trend should be a rapid increase in the early stage, a gentle growth in the middle stage, and a basic stability in the later stage.

If the defect does not increase in the early stage, but in the middle and late stage, then it is necessary to analyze whether it is due to the failure to fully invest manpower and time in the early test, or the problem of testing attitude and ability, or the defect caused by the adjustment of the design by the students in the middle of the test.number increases.

2. Problems after testing

The standard of the test should be to pass the regression test, and the new function can be used normally.If there is a problem of blocking and dangerous level after the test, it is necessary to analyze whether the quality of the test is not strictly controlled, and there is no clear acceptance standard.

3. Is there a serious problem that was discovered after a few days of testing

Observe whether serious and above problems are discovered and solved in the early stage. If there are serious problems raised after a few days of testing, it depends on whether the testing strategy is reasonable and whether it is not executed first and has a higher priority.test point.

4. Defects caused by development and repair problems

Some test cases are fine at the beginning of execution, but there is a problem later, which is most likely caused by the developers when they fix the problem.After each developer submits the code, the tester needs to look at the code changes and evaluate the scope of influence.

If conditions permit, put this step forward: communicate with the development classmates about the solution to the problem to reduce the risk.

5. Pending Defects

Pending defects are generally functions that do not need attention, or are discussed and supplemented in the next iteration. If so, consider why the three parties have inconsistent understandings, and why the previous requirements review, design review, and use case review did not find it.This point only appears during testing.

6. Whether the defect type is single

Testing students not only need to find requirements and design loopholes, but also pay attention to interface and interaction deficiencies and propose optimization suggestions.

7.Which module has more defects

Module with more problems, more problems to be found.In the testing phase, you need to focus on modules with more defects and design more scenarios to cover them.At the same time, this also requires that the defect management panel needs to provide the function of module classification, and when submitting a defect, you also need to standardize the module to which the problem belongs.

8. Proportion of defects above important level

If a project has a high proportion of issues above the critical level, it means that the development quality needs to be improved. At this time, it is necessary to analyze whether the development time is compressed or the newcomer is not familiar with the business. The development manager needs to pay special attention to such projects.

9. Are all bugs resolved/closed after going online

Every day, the person in charge needs to remind the relevant development and testing students to deal with the defects and update the defect status in time. All defects should be closed (or a few suspended) before going online. If not, the person in charge needs to remind them again.

It's not difficult to look at defect analysis in this way, is it?Careful to discover, you can explore more and more interesting questions.

It is important to find out the test strategy problem and correct it in time to avoid repeating the same problem next time.Also, a few points to keep in mind:

First, the defect standards need to be unified, otherwise everyone's evaluation standards will be different, which will affect the accuracy of the analysis results;

Second, test students need to record defects in the project. Don't silently find developers offline to solve them. This will not only easily lead to forgetting to return, but also lead to inaccurate project summary evaluation.

Finally: You can get a 216-page software test engineer interview collection document on the public account: Programmer Yifan [free].And the corresponding video learning tutorials are shared for free!, including basic knowledge, Linux essentials, Shell, Internet program principles, Mysql database, packet capture tool topics, interface testing tools, advanced testing-Python programming, Web automated testing, APP automated testing, interface automated testing, testingAdvanced continuous integration, testing architecture development testing framework, performance testing, security testing, etc.

Now I invite you to join our software testing learning exchange group: 769146372, remark "join the group", everyone can discuss and communicate software testing together, learn software testing techniques, interviews and other aspects of software testing, and there will be free live classes, to gain more testing skills, let's advance Python automated testing/test development together, and move towards a high salary.

Friends who like software testing, if my blog is helpful to you, if you like my blog content, please "Like", "Comment" and "Favorite" with one click!