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

1. I can't reproduce this bug here.

Solution.

Bug should be concise and to the point. If there is any ambiguity in the description, be sure to summarize it and improve it as soon as possible. Sometimes you will encounter probabilistic bug, so you should tell the probability of development and provide as many conditions as possible for reproduction.

When repeating the problem, I hope to be able to roughly judge several problem points, and then communicate with the testers, how to capture information and capture that kind of information? Is it possible to provide a debug version for reproduction, or to add a print information version according to the predicted point?

2. This is not a code problem. This is how the requirement is defined.

Solution.

The demand is also determined by the person, if you feel any objection, you can ask the demand personnel to find out why it is defined in this way, tell them what you think, and see how they decide. If you are convinced by the demand, of course, it is best, if you still do not agree with the view of the demand, and the demand does not agree with my proposal, then you can only listen to him. After all, he has the power. But we can keep a record of communication to prove that ambiguity has occurred here.

3. Someone else is in charge of this piece, and there is no problem with my part.

Solution.

If bug is distributed to programmers by the development project manager, it is the project manager who faces the problem, not testing. Of course, the project manager certainly has the project manager's approach. However, what should we do if the test encounters such a problem? invite the developers responsible for the relevant content to a discussion group and let them discuss it on their own, so that it is clearer and there is no need to transfer here. If they all think the code is fine, and I have a strong screenshot and truth, then I have to hand it over to the superior and let them decide how to solve it.

4. Is there a problem? (that is, the developer does not think this is a problem)

Solution.

Testers must be more sensitive than developers and have less tolerance for bug. Especially some bug that do not conform to the user's habits, the development always feels no big deal. For example, the default width of a list is so small that it opens for the first time, and some content is hidden behind it, but the width can be adjusted manually. Developers feel that the problem is small, does not affect functionality, and there is a solution, so they do not think it is bug. At this time, it's time to give full play to your testing skills, be sweet, say nice things, and have a gentle attitude. Because since it is a small problem, it must not be difficult to solve, just patiently urge the development to change it. Push once, not twice. Remember to have a good attitude.

5. Users will not operate like you!

Solution.

No one can predict how the user will operate. It is not possible for us to cover all the possibilities, but most users will appear in the operation, of course we have to test. Slowly bring the development out of the code world, to the user's world, let him think from a different point of view, after all, software development is not to achieve functions, but to meet the needs of users. If you fail to convince him in the end, first report to your superiors, second, make a good record of communication, and back it up in the test report in the future.

Reference: how to communicate http://www.studyofnet.com/news/948.html in Software testing

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.