Menu
From time to time we get bugs on production that can be fixed by for example by changing a configuration, disabling some part of the logic, and such.
I've argued with my manager that we should reproduce the bugs locally to ensure the fix works, and more importantly so developers and QA can include the check for these cases as part of the regular release.
My manager thinks is a waste of time, as the solution works so there is no need to reproduce locally.
So: Should we try to reproduce locally to verify the fixes ? Any pointers on how to sell this point to my manager if you agree with me ?
917
If the bug is not reproducible, then the testing effort used in finding, analyzing and reporting that particular bug/defect is a total waste. For understanding and reproducing a bug, it is essential to have detailed and properly explained 'Steps to Reproduce', state and environment in which the bug occurred.
What is bug reproduction? Bug reproduction, or issue reproduction, is exactly as it sounds—it involves a software tester reproducing the bug in your software. They replicate the exact scenario that caused the bug to appear, and then determine how it affects your software.
Taking some extra time to verify that you have the right steps to reproduce an issue is crucial to preventing a bug being passed around between teams. Not only will that delay the fix, but it can also cause frustration for the individuals attempting to chase down the issue.
Answered On : Jul 19th, 2006. Reproducing Bug means the defect/Bug reappears at dev environment then they will resolve and fix the Bug. Bug is not reproducable at dev environment then we will send the Execution steps with appropriate Screen shots clearly.
If you haven't reproduced the bug, your "fix" is nothing better than a guess.
133
Off the top of my head:
24
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
