Common problems encountered in software testing and communication methods

1. I can't reproduce this bug here.

Solutions

the Bug should be concise and stress-focused. If there is ambiguity in the description, be sure to summarize and improve as soon as possible. Sometimes you encounter a probabilistic bugthat tells you what the development probability is and provides as much of a reproducible condition as possible.

in reproducing the problem, I want to be able to roughly judge a few problem points, and then communicate with the tester, how to capture information, capture that kind of information? do you provide a debug version to reproduce, or to increase the print information version based on a pre-determined point?

2, this is not a code problem, requirements so defined

Solutions

Demand is also determined by people, if you feel the objection, you can find the needs of people to ask clearly, why the definition of their own ideas to tell them, see how they decide. If the need to persuade the best of course, if they do not agree with the demand of the view, demand and disagree with my proposal, it can only listen to him, after all, power in him. But we can keep a record of the communication and prove that there has been ambiguity here.

3, this piece is responsible for others, I am responsible for the part of no problem

Solutions

if a bug is distributed to programmers by a developing project manager, it is the project manager who is facing the problem, not the test. Of course, the project manager certainly has the project manager's approach. However, the test encountered such a problem how to do, the responsible for the development of the relevant content invited to a discussion group, let them discuss themselves, so that more clearly, do not have to relay in the test. If they all feel that the code is not a problem, and I also have a strong and the truth, it is only handed over to the superior leadership, let them decide how to solve.

4.do you have any questions? (That is, development doesn't think it's a problem)

Solutions

testers must be more sensitive than development and less tolerant of bugs. In particular, some do not conform to the user's habit of the bug, development always feel that there is no major obstacle. For example, a list default width is too small, causing the first open, some content is hidden behind, but this width can be manually adjusted. Development feels that the problem is small, does not affect the function, but also has the solution, therefore does not think is the bug. This time, it is necessary to play the test of the ability, sweet a little, say good words, gentle attitude. Since it is a small problem, it must not be difficult to solve, patiently urged the development of the rehabilitation of the good. Urge once not to rush two times, remember attitude must be better.

5, the user will not operate like you!

Solutions

No one can predict how the user will operate. We can't cover all the possibilities, but most of the users will get the action that we certainly want to test. Slowly the development from the Code of the world brought out, to the user's world, let him change a point of view, after all, software development is not to achieve the function, is to meet the needs of users. If the last still failed to persuade him, the first to the superior, the second good communication record, in the future backup in the test report.

The above is the software testing encountered common problems and communication methods, if you feel trouble can consider using some APP Automated test tools: www.ineice.com

Common problems encountered in software testing and communication methods