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

It is believed that most IT testers have some problems communicating with developers when they apply for bug. Here are some tips from veterans to newcomers on how to persuade developers to accept your bug more effectively:

1. First of all, make sure that these are real bug.

Do not appear due to configuration reasons or operational errors caused by the "bug", this will be "despised" by the developer. Testers should try to be professional, try not to make trouble for developers, do not create bug that does not exist, and do not submit duplicate bug.

2. Write a good bug description. Ensure that the process of BUG can be reproduced according to bug description.

This is important! Sometimes when a developer sees an inexplicable bug that is not clearly described and cannot be reproduced, he will be very angry. This will directly affect the image of the tester in the developer's mind. Since we submit this bug, we must be responsible for it. Bug describes accurate, unambiguous, detailed and concise reproduction steps, and bug screenshots are necessary. If it is special test data, we also need to attach these data. For example, the picture data of 2049KB. For the problem of low recurrence rate, we need to note the occasional occurrence and record the environmental information at that time in detail. Such as operating system, product name, version, operation procedure, whether the machine is related, whether the product is related, and so on.

3. Improve your professional skills.

We should try our best to improve our personal skills. I'm not talking about learning about testing frameworks or automated performance testing tools, which can be learned later. We need to ensure that the most basic thing is the ability to analyze the business. To be fully familiar with all aspects of our software product business, including functional business, code implementation logic, environment configuration and deployment, etc. If you understand that operations like recharging must have real access to the third-party payment platform interface, then you will know why there is an exception in the payment page jump interface during the test. it will naturally be clear that this is not a problem with the code, but is not configured. You won't have the problem in point 1. And it will be more reasonable when persuading developers to accept your bug.

4. The key points should be grasped in the test.

Testing should be focused on, don't test too much in unimportant places, and don't waste communication costs on the so-called "bug" that doesn't matter. What is the key point is the main function of the product and the operation that users often use. If it is a serious problem with clear requirements, I believe that as long as it is a developer, he will try to fix it. But for example, some serious problems caused by unconventional operations, developers will say that in the actual scenario, users will not do this. For these problems, communication is a waste of cost, and the problem can be recorded in a daily newspaper and fed back to the test boss or project leader for evaluation. For example, some personal interface suggestions, we can submit bug, but the development does not change, nor does it affect the use of users, we do not have to struggle too much.

5. the questions are concentrated for consultation and development.

Developers are also busy, so don't send a qq message as soon as you find something you don't know. Because when you are busy, to a large extent, the problems you throw away will sink into the sea. Sort out the questions you personally need to ask and gather them to ask the developer. In order to communicate efficiently, it is best to communicate face-to-face with the developer (unless you need to retain screenshot evidence). Make an appointment with the developer and go directly to the public office to find him. This method is especially feasible if you are a good-looking person or a cute person.

6. Be a smart tester

Pay attention to the tone of communication with the developer

There must be a way of thinking in empathy, doing things not for people, and dealing with things must have a tolerant heart. Only in this way can we persuade R & D to modify Bug.

B. Have a good personal relationship with developers.

Once the relationship is good, it's easy to say anything, and he won't find you annoying. But just because the relationship is good, bug should not directly narrate it orally and do not submit it to the bug platform to make statistical records.

The above suggestions are mainly for testers. I hope they will be helpful to your workplace. Whether it is testing or development, it is to better improve the product, and think about it from each other's standpoint. Our life is still very good.

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.