What to do when programmers don't modify bugs? I teach you

Catalog

1、 Preface

2、 Analysis of current situation

3、 Why are programmers unwilling to modify bug？

4、 Why are our testers upset ？

5、 Why is it difficult for us to persuade programmers to modify those bug？

6、 How to persuade developers to correct bug？

7、 Add

8、 in addition , The author believes that the following measures will help promote bug The solution of the ：

9、 Be careful

---

1、 Preface

Today's topic , All testers will experience , I've been distressed by this . The author takes this opportunity to talk about his views , Do not seek to solve the current situation , I just hope that readers will have less trouble after reading this article .

2、 Analysis of current situation

not long ago , A testing old man beside the author raised a defect of printing text overflow , But the person in charge of the defect , A young programmer has no time to modify the project as it is nearing its launch , And the defect has little impact and is rejected , And the text says （ A tough complaint ）, The testing expert insisted from the beginning to the end and was helpless to compromise , Let me feel a lot .

                   

 

3、 Why are programmers unwilling to modify bug？

Nothing more than no time , The problem is too small , Can't reproduce , Can't understand , It is unlikely to happen in the actual environment , The problem only occurs in the very special device configuration that no one uses , The risk of correcting defects is too great （ Especially near the cover ）, It will not affect the actual users of the program .

4、 Why are our testers upset ？

Maybe it's before the seal bug It should all be solved （ Obsessive compulsive disorder ）, It may also be that programmers don't understand bug The seriousness of , May be bug Obviously violate the specification , It may also be that the defect will definitely affect users .

5、 Why is it difficult for us to persuade programmers to modify those bug？

Tell me what I saw ： The tester is too persistent （bug It is not necessary to modify ）, Testers don't know the skill of persuading programmers , Testers look down on themselves （ Once programmers are strong , The tester is humble ）, The technical level of testers is low （ Unclear modification bug Cost of , Maybe just adding a field can fix , Development costs a lot , The tester thought it was really big ）.

Countermeasures

Countermeasures should have followed the classification of problems , After analyzing the root causes, answer one by one . However, this article is not a rigorous academic report , The author will only talk about some general measures .

6、 How to persuade developers to correct bug？

• Explain how the problem will affect the normal use of the product ？
• What data will be destroyed ？
• How often users encounter this problem ？
• Comments on similar products in the market
• Point out the troubles caused by similar problems to customers
• Multi reference data collected by technical support
• Previous versions have passed the test of this function
• Communicate with other project stakeholders . Find out who is most affected if the program error is not modified （ Or people who benefit from the modification ）, Determine how much trouble program errors will cause them . Let those who care about this module persuade .
• List some scenarios , Explain the program errors that reasonable users will encounter when using the program properly , Or questions .
• Add some follow-up tests , Look for the more serious consequences of this program error , Or look for situations that occur in a broader context than described in the error report .

                           

 

7、 Add

1. Make some additions to the last point above ： If the programmer does not modify a bug And we decided to refute , Don't rely entirely on the language and information in your initial test report . Try to do some supplementary tests , Or give more effective examples , Otherwise, you will not only waste your time , And damage your reputation , Influence one's own persuasion .
2. Don't insist on modifying all bug. The project manager may be because of the risk 、 Cost and other reasons , Refuse to modify some bug, In this case , We testers don't need to insist on modifying all defects , Unless you can explain the serious risks that a defect may introduce .

8、 in addition , The author believes that the following measures will help promote bug The solution of the ：

1. Develop good report writing habits ： For example, describe various configurations of problems in the report （ Need to verify ）, Or predict some possibility and provide relevant information in the report （ Especially those that are difficult to reproduce bug） . Good error reporting will drive problem correction .
2. Wait a minute , Look at your feedback during the review , With static brake , Provide additional information .
3. Use facts and data more , for example “ A similar system also has this problem , The customer because of that problem , There is a lot of opinion about the procedure , Because customers waste on average every week XX Time is above ”
4. Learning to program , understand bug Cause of occurrence , Help write better reports , And understanding bug Repair costs .

9、 Be careful

1. About using bug The management system monitors the performance of programmers . Some test managers try to use bug Track data to encourage programmers to modify bug, For example, use data to feedback whether a programmer has a large number of bug not changed , Or whether the modification time is too long , Or whether it is always delayed . The author will not comment on whether this system should be implemented , However, the author suggests that we should pay attention to guiding programmers' emotions when implementing , Otherwise, it is easy to cause some programmers' disgust , They will exaggerate the incompetence of testers at some time , Or make remarks against the testing department . But it's normal ,bug As long as management tools are used for administration or personnel management , Instead of technical management , These problems will arise .
2. close bug The authority of should be controlled in the hands of the tester . Unless verified by the tester , otherwise bug Can't be closed-loop . In some cases , Programmers will fix the unrepaired bug Set as “ Postpone the amendment ”、“ Non procedural errors will not be modified ”“ Repeated defects shall not be modified ”, Testers need and are obliged to question this .
3. Try to avoid “ Postpone the amendment ” Turn into “ Never change ”. In many companies ,bug Marked as “ Postpone the amendment ” That means “ Never change ”. To avoid this situation , A feasible measure is to put forward these defects in the next version of the project scope Review , At that time, the schedule pressure was the least , And the project manager is also the most rational 、 Most sober . in addition , Find out “ Postpone the amendment ” Of bug after , If you disagree , It is recommended to communicate with the test manager or project manager as soon as possible .
4. bug Verify as soon as possible after modification , Communicate with programmers as soon as possible after the return fails , Otherwise, the longer the time is delayed , The less programmers remember .
5. If bug Repeated returns failed , Or serious defects are found near the closure , Not only in defect management tools , You should also directly find the corresponding programmers to communicate .

        

 

Thank everyone who reads my article carefully ！！！

If you can use the following information, you can take it away directly ：

1、 Self study development or test the necessary complete project source code and environment

2、 Test all templates in the work （ test plan 、 The test case 、 Test report, etc ）

3、 Classic interview questions for software testing

4、Python/Java Automation test practice .pdf

5、Jmeter/postman Interface test full set of video acquisition

I personally sorted out some technical materials I have sorted out in my software testing career in recent years , contain ： e-book , Resume module , Various work templates , Interview treasure , Self study projects, etc . If you encounter problems in your study or work, you can directly join the group and ask , There will also be great gods in the group to help solve ,

Collect information 、 Great God answers 、 Exchange learning, click the link to join the group chat 【python Automated test communication 】：https://jq.qq.com/?_wv=1027&k=Rt8JGuiw