Welcome to Scribd. Sign in or start your free trial to enjoy unlimited e-books, audiobooks & documents.Find out more
Standard view
Full view
of .
Look up keyword
Like this
0 of .
Results for:
No results containing your search query
P. 1




|Views: 150|Likes:
Published by anon-942623

More info:

Published by: anon-942623 on May 31, 2007
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less





The Fine Art of Writing a Good Bug Report
Rex Black RBCS, Inc.31520 Beck RoadBulverde, TX 78163Phone: +1 (830) 438-4830Fax: +1 (830) 438-4831HTTP: //www.rexblackconsulting.comE-mail: Rex_Black@rexblackconsulting.com
Stable fly photo courtesy of
Quality Week 2000Copyright (c) 2000, Rex Black, AllRights Reserved2
What Is a Bug Report and WhyDo We Write Them?
Bug report is a technical document
Describes failure mode in system under test (SUT)The only tangible “product” of testing
Not a management problem escalation tool
“Build not delivered on time” is not a bug report summary“Build 781 fails to install” is a bug report summary
Written to increase product quality
Documents a specific quality problem quality of SUTCommunicates to developers
Quality Week 2000Copyright (c) 2000, Rex Black, AllRights Reserved3
Are Bad Bug Reports a Problem?
Anecdotally, developers return many bug reports asunreproducible, leading to:
Wasted time writing the reportFrustration for tester and developer alikeNo increase in product quality
Bug reports can be unreproducible due to:
IntermittenceInconsistent test/development environmentsDisputes over “correct” behavior
But many unreproducible bug reports are poorlyconceived and poorly written

Activity (8)

You've already reviewed this. Edit your review.
1 thousand reads
1 hundred reads
Terah Stephens liked this
venkat4u4u liked this
Arjun12345 liked this
vishal_rkgit liked this
vishal_rkgit liked this

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->