Timeline for Why are reproduction steps helpful for fixing software bugs?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 17, 2021 at 15:56 | comment | added | Chris | Sometimes I call whoever raised something I can't repro to help me understand. If it still can't be repro'd, I sometimes hear the objection "well the steps are wrong but it's definitely broken, why can't you fix it?" I trust that they're right that there is a bug somewhere, but I still can't do anything until someone works out the steps. I have to reject this bug as can't repro, but I don't want to be saying "we need steps because I said so", I want to be able to explain why the steps are a prerequisite to my doing anything. Screen share or not makes no real difference to the conversation. | |
| Jun 17, 2021 at 14:30 | comment | added | Doc Brown | @Chris: writing a ticket should be responsibility of the support team, but adding the missing details to make the ticket useful is something a dev together with the support member should do. Screen sharing is not a replacement for this, but it supports the process tremendously. | |
| Jun 17, 2021 at 14:09 | comment | added | Chris | At the risk of implying our software is hugely buggy, if I had a screen share for every bug that came in I'd get nothing else done, and I'd still have to write it up so that someone could do the work. All this would do would be to shift the responsibility of writing the ticket from support to dev. | |
| Jun 17, 2021 at 13:54 | history | edited | Doc Brown | CC BY-SA 4.0 |
added 481 characters in body
|
| Jun 17, 2021 at 13:42 | history | answered | Doc Brown | CC BY-SA 4.0 |