Shulou(Shulou.com)06/03 Report--

Every time I mention a requirement, I BUG every time I disagree with the developer. Once saw a joke, told me, quarrel is no good! Affect the mood, the correct posture of the bug should be like this:

Don't tell programmers that your code has BUG.

His first reaction is: 1, there is something wrong with your environment; 2, can you use it when you step on a horse?

If you say euphemistically: your program is not what you expected, see if my method is different.

He instinctively thinks: is there a BUG in the program?

After reading it, I felt better immediately. However, I am an independent-minded person, so the above is just a communication skill to assist BUG. It is also important to know how to correctly describe BUG in my actual work. I would like to share with you

1. Existence of BUG

When the tester encounters a problem, don't rush to confirm whether it is BUG or not. Follow up and analyze the problems encountered, verify that there are no errors in the environment configuration and actual operation, confirm the BUG and submit it to the developer.

2. BUG randomness

In the case of confirming the existence of BUG, confirm whether the BUG can be reproduced:

a. Can be reproduced, find out the law of reporting development, at the same time summarize the problem, the probability of the same problem in different modules, whether the follow-up will cause correlation problems, and so on.

b. It is difficult to reproduce, carefully describe the problem and explain the randomness. For example, when I am doing module testing with selenium and TestWriter, I describe the correct problem with its developers.

3. Write BUG report

A clear BUG title and a clear description of BUG are necessary for testers to report to BUG:

A. simplify the description so that the developer or project manager can see what the problem is.

B. Briefly describe the test steps, actual test results, expected test results and conclusions when bug occurs

Describe the comparison and description of expected and actual results. For example: "when you automate testing and execute the plan with TestWriter, when you click on the scheduling plan, the browser pops up, and the plan shows the assignment, when in fact it shows the plan to be assigned." When using selenium, users who operate the page cannot log in, but they can actually log in.

It is not enough to have skills, but also need to learn to communicate with developers in a timely manner to verify whether the proposed BUG is modified or not, so as to ensure that the situation will not happen in the future.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.