The communication problem in software testing work

From the beginning, testing needs to focus on demand. Often in the discussion of design, development and requirements can easily ignore the test members, who subconsciously feel that this is not a test of what. However, testing should also be familiar with the business, familiar with the function, familiar with various design, and testing needs to stand in the user's perspective to consider whether their design has unreasonable place, and put forward their own suggestions. These work, test members need to take the initiative, actively participate in, more constructive comments, which may allow development to slowly discover the importance of test members.

Second, the most frequent communication should be the discussion of bugs. Here are a few of the communication problems encountered, and my solution.

1, "This bug my side can't reproduce ah ~ ~ ~"

Solution: This problem first to introspection, the bug description is not clear. 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 bug that tells you what the development probability is and provides as much of a reproducible condition as possible.

2, "This is not a code problem, requirements so defined"

Solution: The demand is also a person, if you feel the objection, you can find the needs of people to ask clearly, why the definition, the idea of their own 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 the responsibility of others, I am responsible for the part of no problem"

Workaround: If the bug is distributed to the programmer by the 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, "Is there a problem?" "(that is, development doesn't think it's a problem.)

Workaround: 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!" ”

Solution: The user how to operate, who are not expected to. 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.

In addition to the problem on the bug, there are test scheduling problems, sometimes small function is not done, or a document, pictures did not upload, and other small functions to do the document upload, it is likely to develop forgot to tell the test. Therefore, in peacetime work, must take the initiative to record problems, active communication and supervision, and repeatedly confirmed, do not be afraid of trouble.

Summing up, testing in the work to actively ask, attitude can not easily compromise, accustomed to be good at recording details, methods on the carrot.

forward to Weibo

The communication problem in software testing work