As a tester, I'm the one who reported the bugs _bug

When testers ask for their needs, they often see that testers and developers have a bug in their words. Then the development of the bombing, tried, recruit fatal.

Once I saw a joke like this:

Don't say to the programmer that your code has bugs.

His first reaction is: 1, you have a problem in the environment, 2, you step on the horse will not use it?

If you gently say: You this program is not the same as expected, you see if my method is not the same.

He instinctively thinks: is the program out of the bug.

It turned out that the jokes were just a joke. Of course, these are just communication tips for reporting bugs, and it's also important to know how to describe bugs correctly.

1, the existence of the bug

Testers in the face of problems, the first reaction do not hurry to confirm whether a bug. Track and analyze the problems, verify the environment configuration, the actual operation without errors, confirm the bug and bring it to the development.

2, the randomness of the bug

Confirm that the bug can be reproduced if a bug exists:

Can reproduce, find out the law of the development of the report, at the same time to summarize the problem, the same problem in different modules of the probability, the follow-up will cause correlation problems and so on;

Difficult to reproduce, detailed description of the problem of randomness, using Testwriter for module testing, and its developers to describe the correct problem;

3, Write bug report

A glance at the bug title and a clear description of the bug are necessary for testers to report bugs:

A Streamline the description and let the development or project manager know what's going on at a glance

b Brief description of the test steps, actual test results, expected test results and conclusions of the bug;

Describe the results in anticipation and actual comparisons as well as descriptions. For example, when you perform an automated test with Testwriter, when you execute the plan, when you click on the scheduling plan, pop-up the browser, plan to show the assignment, and in fact show the plan to be allocated. "These are not finished, but also need to learn the timely and development of communication, the proposed bug to verify whether to make changes to ensure that the situation will not occur, a complete solution." I think being a tester is worth thinking about.