As a tester, every time I raise requirements, I often see bugs when testers and developers disagree . Let the development fry the pot every time.
So, I saw this paragraph on the Internet that said:
Don't tell the programmer that your code has bugs .
His first reaction was: 1. Is there something wrong with your environment? 2. Will you use the horse ?
If you say euphemistically: your procedure is not the same as expected, you can see if my method is different.
He instinctively would think: Is there a bug in the program?
Facts have proved that the development has long known, so the joke is just a joke. In fact, these are just communication skills to assist in reporting bugs . In actual work, you still need to know how to correctly describe bugs and find problems, which is the kingly way~
1. The existence of BUG
When the tester encounters a problem, the first reaction is not to rush to confirm whether it is a BUG . Track and analyze the problems encountered, verify the environment configuration and the actual operation without errors, confirm the bug and submit it to the development.
2. BUG randomness
In the case of confirming that the bug exists, confirm whether the bug can be reproduced:
a. Reproducible, find out the rules and report for development , and summarize the problems at the same time, the probability of the same problem appearing in different modules, whether it will cause correlation problems in the future, etc.;
b. Difficult to reproduce, carefully describe the problem to illustrate the randomness, and describe the correct problem with its developers when using TestWriter for module testing;
3. Write a bug report
A clear bug title and a clear description of the bug are necessary for testers to report bugs :
a . Streamline the description so that the development or project manager can see at a glance what the problem is
b . Be concise, describe the test steps where the bug occurred , the actual test results, the expected test results and conclusions;
Describe the comparison of expected and actual results as well as instructions. For example: " When using TestWriter for automated testing, when the plan is executed, when clicking on the schedule, the browser pops up, the plan shows the assignment, and in fact it shows the plan to be assigned. "
The above is not over yet, you still need to learn to communicate with the development in a timely manner, and verify whether the bugs mentioned are modified to ensure that the situation will not happen in the future and be completely solved.