Comments on: Defective Bug Reports http://www.testingmentor.com/imtesty/2009/11/10/defective-bug-reports/ Treatises on the practice of software testing Tue, 07 Feb 2012 09:15:11 -0500 hourly 1 http://wordpress.org/?v=3.1.3 By: testingmentor http://www.testingmentor.com/imtesty/2009/11/10/defective-bug-reports/comment-page-1/#comment-10 testingmentor Tue, 10 Nov 2009 07:31:54 +0000 http://testingmentor.com/imtesty/2009/11/10/defective-bug-reports/#comment-10 I agree that the product life cycle and organizational demands (or values) dictate how much time a person spends investigating certain bugs. But, I respectfully disagree with your statement that "Good testers write consistenly good bugs, excellent testers write the best bugs for the cicumstances [sic]." In fact, one of the hallmarks of 'excellent' professional testers is consistency! Tuesday, June 02, 2009 1:56 PM by I.M.Testy I agree that the product life cycle and organizational demands (or values) dictate how much time a person spends investigating certain bugs.

But, I respectfully disagree with your statement that “Good testers write consistenly good bugs, excellent testers write the best bugs for the cicumstances [sic].”

In fact, one of the hallmarks of ‘excellent’ professional testers is consistency!

Tuesday, June 02, 2009 1:56 PM by I.M.Testy

]]> By: testingmentor http://www.testingmentor.com/imtesty/2009/11/10/defective-bug-reports/comment-page-1/#comment-9 testingmentor Tue, 10 Nov 2009 07:31:33 +0000 http://testingmentor.com/imtesty/2009/11/10/defective-bug-reports/#comment-9 It's important to do investigations for each bug, but the product life cycle should dictate how much. Right after code complete it's probably better to get all the issues logged quickly, rather than take hours with each bug and lovingly delve into each one. Teams have different bandwidth at different times. When the test team is slammed, it's wise to offload investigation to Dev and PM where possible. Likewise, when the developers are in high gear, the test team should be extra diligent with the details in bugs to streamline bug fixes. Good testers write consistently good bugs, excellent testers write the best bugs for the cicumstances. Wednesday, May 27, 2009 3:05 PM by SaintD It’s important to do investigations for each bug, but the product life cycle should dictate how much. Right after code complete it’s probably better to get all the issues logged quickly, rather than take hours with each bug and lovingly delve into each one.

Teams have different bandwidth at different times. When the test team is slammed, it’s wise to offload investigation to Dev and PM where possible.

Likewise, when the developers are in high gear, the test team should be extra diligent with the details in bugs to streamline bug fixes.

Good testers write consistently good bugs, excellent testers write the best bugs for the cicumstances.

Wednesday, May 27, 2009 3:05 PM by SaintD

]]>