Comments on: The Importance of Resolution in Bug Systems http://thetesteye.com/blog/2009/06/the-importance-of-resolution-in-bug-systems/ by rikard edgren, henrik emilsson, martin jansson and friends Fri, 10 Sep 2010 09:30:15 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Henrik Emilsson http://thetesteye.com/blog/2009/06/the-importance-of-resolution-in-bug-systems/comment-page-1/#comment-150 Henrik Emilsson Tue, 07 Jul 2009 09:22:34 +0000 http://thetesteye.com/blog/?p=303#comment-150 @Rikard: What happened with the old expression "It is better with a really good bug report than a good bug report"? :-) @Rikard:
What happened with the old expression “It is better with a really good bug report than a good bug report”? :-)

]]> By: Rikard Edgren http://thetesteye.com/blog/2009/06/the-importance-of-resolution-in-bug-systems/comment-page-1/#comment-138 Rikard Edgren Wed, 17 Jun 2009 21:57:02 +0000 http://thetesteye.com/blog/?p=303#comment-138 I totally agree. Sometimes you can hear things like "It is better with a bad bug report than no bug report at all". The answer is: "It is better with a good bug report than a bad bug report." Leaving fields at default (e.g. Priority and Severity) is probably the most common laziness. I totally agree.
Sometimes you can hear things like “It is better with a bad bug report than no bug report at all”.
The answer is: “It is better with a good bug report than a bad bug report.”
Leaving fields at default (e.g. Priority and Severity) is probably the most common laziness.

]]> By: Martin Jansson http://thetesteye.com/blog/2009/06/the-importance-of-resolution-in-bug-systems/comment-page-1/#comment-137 Martin Jansson Tue, 16 Jun 2009 16:41:23 +0000 http://thetesteye.com/blog/?p=303#comment-137 I agree that Resolution is important. But nearly everything in the bug system is important. If the bug reports are sloppy they tend to create conflict between those who are dependent on the information. If fields such as priority, severity are not entered correctly they might not be recognised directly as important. If you report on the wrong product, project, sub-component etc there is also a big chance that they are noticed too late. As a tester, bugs are one of most important byproduct of our craft. By neglecting this important I say we do not act like proffessionals. I would not say that I am personally offended by a tester who is sloppy about bugs, but I would indeed go through with him/her a few war stories about the cost of bad bug reports. I agree that Resolution is important. But nearly everything in the bug system is important. If the bug reports are sloppy they tend to create conflict between those who are dependent on the information. If fields such as priority, severity are not entered correctly they might not be recognised directly as important. If you report on the wrong product, project, sub-component etc there is also a big chance that they are noticed too late.

As a tester, bugs are one of most important byproduct of our craft. By neglecting this important I say we do not act like proffessionals. I would not say that I am personally offended by a tester who is sloppy about bugs, but I would indeed go through with him/her a few war stories about the cost of bad bug reports.

]]>