Timeline for Best guidelines for bug reporting?
Current License: CC BY-SA 4.0
14 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 13, 2020 at 11:22 | history | edited | JAINAM | CC BY-SA 4.0 |
deleted 2 characters in body
|
| Sep 9, 2016 at 4:07 | history | edited | pgraham | CC BY-SA 3.0 |
Revert edit that changed the intent of my answer but also add some explanation about why I didn't like the changes
|
| S Sep 7, 2016 at 13:38 | history | edited | Kate Paulk | CC BY-SA 3.0 |
Cleaned up & reformatted expected materials to better reflect the editors' intent
|
| S Sep 7, 2016 at 13:38 | history | suggested | CommunityBot | CC BY-SA 3.0 |
Changes on my view.
|
| Sep 7, 2016 at 12:22 | review | Suggested edits | |||
| S Sep 7, 2016 at 13:38 | |||||
| May 18, 2016 at 4:09 | comment | added | kalingga | Customer's defect report is something that hard to be reproduced! Mostly they only provide "title of the problem". I think reoccurence rate is also important information. I found a lot of problems that only happen "once"! | |
| Jun 25, 2012 at 18:01 | comment | added | pgraham | @dzieciou When I'm debugging a problem I expect there to be some back and forth. If I'm unable to reproduce a problem then I will care about environment, versions, etc. for the initial report anything more is unnecessary until I cannot reproduce the problem | |
| May 11, 2012 at 2:27 | comment | added | user867 | @ckenst More importantly, if there's a discrepancy between what's supposed to happen and what the tester thinks should happen, the tester is unlikely to be aware of it, and therefore can't be expected to incude that information in the report. | |
| May 11, 2012 at 2:25 | comment | added | user867 | @ckenst I submit that knowing what the tester expected it to do is a more valuable addittion to test report than what it's actually supposed to do: If you don't know what it's supposed to do, knowing what the tester thought it was was supposed to do can be a big help. And if you do know what it's supposed to do, knowing what the tester thought it was supposed to do can help you spot spot gaps in tester understanding and education. Either way, there's a gain. | |
| Mar 29, 2012 at 23:31 | comment | added | Chris Kenst | You don't need to know what it's supposed to do, just what the person filing the bug report thinks the result should be? | |
| Mar 27, 2012 at 2:50 | vote | accept | Todd Ditchendorf | ||
| Mar 27, 2012 at 2:49 | comment | added | Todd Ditchendorf | This is actually my favorite answer so far. But it's missing two steps: 0: Search first (optional, but strongly encouraged) 0.5: provide complete system information (what device are you using? what version of relevant software [like OS and app]). | |
| Mar 26, 2012 at 20:58 | comment | added | Joe Strazzere | Don't you find a need for a description of the problem? | |
| Mar 26, 2012 at 20:32 | history | answered | pgraham | CC BY-SA 3.0 |