Timeline for How to respond to requests to retest, in hope that the bug is gone?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 17, 2019 at 18:39 | comment | added | Dragonel | The bug was fixed - you had a secondary issue that the deployment was incorrect, but that doesn't mean you lied about fixing it. | |
| Nov 14, 2019 at 22:03 | comment | added | CJ Dennis | @Dragonel I'll give you an example. I fixed a simple bug and proved it in one environment. I merged the code without conflicts, tagged it, and deployed the tagged commit to another environment. The bug was not fixed. It took a while to discover I'd accidentally tagged the pre-merge commit instead of the post-merge commit. Human error can occur at any time, even on simple tasks. | |
| Nov 14, 2019 at 21:51 | comment | added | Dragonel | "Any programmer who tells you there is a 100% chance that a particular bug is fixed is lying" No, there are bugs you can be certain of, and others you can't. It depends on the complexity & how reproducible the bug was. If it reproduced 100% of the time and now it doesn't happen in multiple attempts, I know I have fixed it. | |
| Nov 13, 2019 at 5:38 | history | edited | CJ Dennis | CC BY-SA 4.0 |
Fix a typo
|
| Nov 13, 2019 at 3:02 | history | answered | CJ Dennis | CC BY-SA 4.0 |