[Software testing] reporting bugs is an art that teaches you how to work with Buddhism.

I believe that most IT company testers have some problems in communicating with developers when reporting bugs. How to more effectively persuade developers to receive your bugs? The following are some suggestions from Senior Veterans:

1. First, make sure this is a real bug.

Do not see "bugs" caused by configuration or operation errors. This will be "despised" by developers. As a tester, we should do our best to be professional and try to make less trouble for development. Do not create bugs that do not exist or submit repeated bugs.

2. Write the bug description. Make sure that you can reproduce the bug process according to the bug description.

This is important! Sometimes the developer will get angry when he sees an inexplicable bug that cannot be reproduced due to unclear descriptions. This directly affects the developer's image. Since we have submitted this bug, we must be responsible for it. The bug description is accurate, unambiguous, and detailed and concise reproduction steps are required. For special test data, we also need to attach the data. For example, 2049kb image data. For the low reproduction rate, we need to specify the occasional occurrence to record the environment information at that time in detail. Such as the operating system, product name, version, operation procedure, machine-related, and product-related.

3. Improve your professional skills.

We should try to improve our personal skills. I am not talking about what testing frameworks and automated performance testing tools I want to learn. I will be able to learn more in the future. First, we must ensure the most basic capability of business analysis. Be familiar with all aspects of our software products, including functional services, code implementation logic, and environment configuration and deployment. If you know that recharge operations are similar, you must have a real third-party payment platform interface, then you know why the payment page Jump interface exception prompt appears during the test. Naturally, you will know that this is not a code issue, but not a configuration. You won't have any problems in the 1st. In addition, it is more rational to persuade developers to accept your bugs.

4. Focus on testing.

Focus on testing. Do not test too much in irrelevant places, or waste communication costs for irrelevant so-called "bugs. What is the focus is the main features of the product, and operations that users often use. If it is a serious problem with clear requirements, I believe that as long as it is development, he will try to fix it. For example, if some Unconventional Operations cause serious problems, developers will say that users will not perform such operations in actual scenarios. Communication is a waste of costs. You can record the problems in the daily report and report them to the test leader or project leader for evaluation. For example, for some personal interface suggestions, we can submit bugs, but the development does not change, it does not affect the user's use, we do not need to worry too much.

5. Concentrate on questions for consulting and development.

Development is also very busy. Don't send a QQ message directly once you find it unclear. It is because when you are busy, the problems you throw in the past will sink into the sea. Sort out the questions you need to ask and concentrate on development. For efficient communication, it is best to have face-to-face communication with development (unless you need to retain evidence ). For about a period of time with the development, go directly to the office to find him. This method is especially feasible if you are a face-to-face or character-loving School.

6. Be a smart Tester

A. Pay attention to the tone of communication with developers

There must be a way of empathy. If you do something right or wrong, you must have a tolerant mind. Only in this way can we persuade R & D to modify bugs.

B. Establish a private relationship with developers.

Once the relationship is okay, he won't bother you. But do not give a verbal explanation of the bug because of its good relationship. do not submit the Report to the bug platform for statistical record.

The above are the suggestions for testers, hoping to help your career. Whether it is testing or development, it is to better improve the product, and think about it from the standpoint of the other party. We still have a wonderful life.

[Software testing] reporting bugs is an art that teaches you how to work with Buddhism.