Home
Updates! What's New?
Got Questions? Get Answers!
QA Overview What is QA?
QA Employment Jobs
Testing Portfolios
Testing Services
Free Consultation
QA Training Become a Tester!
QA Course List
Testers The QA Elite
The Beta Tester
The Game Tester
The Software Tester
Testing SQA Glossary
Types of Testing
QA Metrics
Forms & Templates
Etc... About Us
Contact Me
Privacy Policy

E-mail Address

First Name (optional)

Then

Don't worry -- your e-mail address is totally secure.
I promise to use it only to send you SQA the Right Way!.

Subscribe To Successful Quality Assurance
XML RSS
Add to Google
Add to My Yahoo!
Add to My MSN
Subscribe with Bloglines
 

5 Most Common Bug Writing Errors: Day #2

Go To: Day 1 - Day 2 - Day 3 - Day 4 - Day 5

If you don’t state the Reproducibility of the bug clearly, then the team will not be able to establish an accurate Priority for it. You must state very clearly whether the bug happens Always, is Intermittent, or has only been Seen Once.

Error #2:
Unclear Reproducibility

Attempt to reproduce the bug enough times to feel confident in the Reproducibility that you state. If it occurs every time, great! Always!

If it only occurs sometimes or most of the time, you must state “how-many-times-it-occurred” out of “how many times you attempted to reproduce it”; the “X out of Y”.

  • 2 out of 10 = 20%
  • 20 out of 100 = 20%

Both of these examples show the same percentage. Which numbers would you have more confidence in? I hope you chose the second one. A sample size of 100 should give you far more confidence than a sample size of 10.

If the bug has only occurred once and you have tried to reproduce it several times, state that. State how many times you attempted to reproduce the bug and were unable to. Then keep this bug in mind so that if you see it again, you can update the information in the bug with your latest results.

As a bonus tip: Keep a ready “Most Wanted” list at your workstation of bugs that you have only Seen Once. This way, if you ever encounter them again, you won’t have to search laboriously through the bugbase to find them.

You can just look at your list, navigate to your bug, and update it with your new information. This will save you a great deal of time and effort as you progress through your projects.

Saving you time from endless searching will mean that you are able to focus on the more important testing and reporting issues. This will make you appear even more efficient and productive; always a good thing for the aspiring Quality Assurance Professional.

Go To: Day 1 - Day 2 - Day 3 - Day 4 - Day 5

Return To Successful Quality Assurance Home


footer for defect entry errors page