Timeline for How to deal with a bug which seems to have fixed itself?
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 12, 2017 at 7:31 | history | edited | CommunityBot |
replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/
|
|
| Dec 2, 2015 at 9:08 | comment | added | gnasher729 | It's all a matter of workload. If you have one bug that was reproducible a month ago and isn't anymore, and another bug that is reproducible now, then you fix the one that is reproducible now first. If you ever get to a state where you are totally bored, then you may investigate. And when the problem comes back by itself, then of course it is a reproducible bug and you start fixing it :-) | |
| Dec 1, 2015 at 17:10 | comment | added | Pete Becker | Problems that go away by themselves come back by themselves. | |
| Dec 1, 2015 at 16:47 | comment | added | Cort Ammon | @ratchetfreak Alternatively, it depends on how serious this particular customer is. If they're singlehandedly funding your paychecks, maybe its worth humoring them ;-) | |
| Dec 1, 2015 at 15:40 | comment | added | ratchet freak | Depends on how serious the bug is. If it's just a layout goof then indeed a couldn't repro stamp and be done, but if it could be more sinister then a few hours to end up with a regression test can be worth it. | |
| Dec 1, 2015 at 15:37 | comment | added | RemcoGerlich | You run the risk of spending several hours on deciding that the bug was already fixed as a side effect of something else, or of not finding anything conclusive at all. I think most people would decide to wait until it is seen in the wild again. | |
| Dec 1, 2015 at 15:35 | comment | added | Paul J Abernathy | In my experience, most teams just check the "cannot reproduce" option in the ticketing system and close it. Testing the "then" and "now" code to ensure the issue was there and no longer is seems like a better solution. But it is also more time consuming than saying "cannot reproduce" and closing it, so it may not be an option for every bug. | |
| Dec 1, 2015 at 14:30 | history | edited | ratchet freak | CC BY-SA 3.0 |
added 3 characters in body
|
| Dec 1, 2015 at 14:28 | history | edited | user40980 | CC BY-SA 3.0 |
Inline linked questions - comments are ephemeral and don't make the reader scroll.
|
| Dec 1, 2015 at 14:22 | history | answered | ratchet freak | CC BY-SA 3.0 |