Exclusive interview with millions of annual salary. What should developers do if they don't fix bugs?

During the test , It is hard to avoid that developers do not want to repair individual for some reasons bug The situation of . When encountered , How should testers push their repair bug Well ？
One 、 Situation analysis

1、 Why developers are not willing to fix bug？

1） Developers and testers are right bug Problems arising from inconsistent understanding of the definition of ;bug The path is deep , Can't reproduce ; Repair bug Big changes , Wide range of influence ; When developers think it is impossible to happen in a production environment 、 Environmental problems , Does not affect the actual user use of the program .

2） Workflow reasons ： Don't have the time , The problem is too small （ Low priority ）, The online time is urgent , Not under my own name bug（ Left by retired developers bug）.

3） Personal ability reasons ： No solution found , Technology is hard to achieve .

4） Objective factors of force majeure , For example, system problems , The third party SDK Questions, etc .

2、 Why are testers upset ？

1） The tester wants all the before going online bug Have been repaired （ Obsessive compulsive disorder ）, Avoid problems in the production environment , Cause irreparable loss .

2） Testers are persuading developers to fix bug when , It is found that the scope of influence is too large , Involving multi-party communication , waste time .

3） The technical level of testers is low , Developers because of the advantages in development technology , There is often a certain bias against the tester . Testers don't have a deep understanding of development costs , It's hard to convince developers to fix bug, For example, a problem that can be solved by adding only one field , Testers don't understand the development workload , Think it's hard , No longer insist on repair bug.

4） Testers are not familiar with the product , Lack of skills to convince developers .

Two 、 How to persuade developers to fix BUG

1、 Be a smart Test Engineer

1） Develop good report writing habits ： take bug The description is detailed and clear , Make sure to reproduce bug The process of , Explain the risk of the problem with facts and data .

2） Follow the test specifications

3） Pay attention to communication skills with developers . In conversation , There should be an alternative way of thinking , It's right to do things, not people , We must have a tolerant heart when dealing with things , That's the only way , To convince developers to fix bug.

4） Personal relationships with developers , As their audience .

5） Learning to program , understand bug Cause and budget bug Repair costs , Improve testing technology
2、 Train of thought

1） explain BUG How will it affect the normal use of the product ？

2） What data will be destroyed ？

3） How often users encounter this problem ？

4） Comments on similar products in the market

5） Point out similar BUG Trouble to customers

6） Multi reference data collected by technical support

7） Previous versions have passed the test of this function

8） The decision is made by the project manager . The project manager may be because of the risk 、 Cost and other reasons , Refused to repair some bug, In this case , We testers don't have to insist on repairing everything bug, Unless you can explain something bug Serious risks that may be introduced .

9） List some scenarios , Explain the program errors that reasonable users will encounter when using the program properly , Or questions .

10） Add some follow-up tests , Look for the bug More serious consequences , Or look for a broader context where this bug The situation of . If the developer doesn't fix something bug, And we decided to refute , Don't rely entirely on the information in your initial test report . Do as many supplemental tests as possible , Or give more effective examples , Otherwise, you will not only waste your time , And damage your reputation , Influence one's own persuasion .

3、 contacts

1） Reverse the thinking of R & D leaders , Attaches great importance to bug, Improve the responsiveness of developers .

2） Communicate with other project stakeholders . find bug Do not repair the most affected people （ Or the person who will benefit most from the repair ）, determine bug How much trouble it will cause them , Let them convince the developers .

3、 ... and 、 summary

bug Repair or not , Testers should have their own principles , At the same time, weigh the pros and cons . Not because you can't push development , Just give up , Let the product take with it bug go online , You can't hold on to a small one bug Don't put , Affect online time .

The house needs to be built layer by layer , Knowledge needs to be learned at one point one . We should lay a good foundation in the process of learning , More hands-on practice , Don't talk much , The last dry goods here ！ I stayed up late to sort out the stages ( function 、 Interface 、 automation 、 performance 、 Test open ) Skills learning materials + Practical explanation , Very suitable for studying in private , It's much more efficient than self-study , Share with you .

Get off w/x/g/z/h： Software testing tips dao

Typing is not easy , If this article is helpful to you , Click a like, collect a hide and pay attention , Give the author an encouragement . It's also convenient for you to find it quickly next time .