An overview of bug analysis positioning in software testing (how QA analyzes locating bugs)

Have you ever met a scene like this?

QA found the problem after finding Dev said:

No, your program is out of the problem!

DEV (after half an hour of tracing):

Well, it's you. Test environment configuration issues

Alas, your data is inconsistent.

Well, it's you. * The program version is wrong

Alas, it's the product line problem.

What about the log?

Was there an anomaly in the CPU?

Can you reproduce it?

It's supposed to be like this here!

Do you expect such a scenario?

QA found the problem, after analysis and judgment, the answers to find Dev said:

Your program out of the bug, the preliminary determination is XX category XX Judge Branch has the question, should take So-and-so's judgment a change on good! --Positioning precision = =

Your program has a bug, the past So-and-so product line has been a similar problem, is a certain function with the wrong, leading to the front-end So-and-so input, will lead to so-and-so abnormal, you check it! --= = = Rich Experience = =

Your program has a bug, it should be so-and-so problem. Page screen, log, system resources, and the steps I have recorded in the bug system, please fix as soon as possible--= = Reasonable

Rd says:

Praise, and you have a very happy cooperation!

What is the significance of QA for bug positioning?

Defining a "problem" is not really a "BUG"

--Question: Inconsistent with expectations, appearances

--bug: Code Error, Essence

Avoid back and forth, improve test repair efficiency

--Low false alarm and clear reason

Helps to understand the internal logical process of the product

Know it and know it

Enhance Dev's trust in QA

--Reliable!

QA to do bug positioning of several misunderstandings:

Mental error: Not aware of the severe, has nothing to do with yourself

--bug positioning is not so big, Sanbang will use on the line

Means of error: positioning must look at the code

--most of the positioning is not code capable

Target myth: All problems should be fixed as bugs

-The problem is not necessarily a bug, that is, you have to consider the cost

Misunderstanding of division of labor: Dev does not need to help QA bug positioning

The goal is consistent, Dev needs to provide testability support

The general process by which QA locates bugs: