A bug development means that the user will not operate like this, and there is no need to repair it. How should testers respond?

Hello, everyone , I'm Daejeon .

 

First , We need to know that if the user really does this , What are the hidden risks , What are the consequences , If the risk is high , The consequences are serious , No matter how low the probability of operation , This BUG  All of them need to be repaired before going online . If development does not fix , We need to make our point clear , Involve product and project managers in joint communication and discussion .

 

secondly , The operation probability is low but the influence range is large , It also needs to be repaired .

 

Last , The operation probability is low and the influence range is small , Tester records BUG , Whether it needs to be modified or communicated with product personnel .
 

All in all , There is no trivial matter about online problems , Try not to make low-level mistakes , The tester should have certain persistence , It cannot be said that the operation frequency is too low to let it go .