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
 

10 Critical Elements of a Bug:
Day #2

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

Here you describe as accurately as possible how often the bug occurs by following the exact Steps to Reproduce.

Element #3:
Reproducibility

There are 3 standard choices:
  • Always
  • Intermittent
  • Seen Once

Those should be the only options that you choose from. Let’s define each option one at a time:

  • Always:
    • By following the Steps to Reproduce, the bug will happen every single time without fail
  • Intermittent:
    • This means that the bug does not occur 100% of the time when following the steps, but has occurred more than once
    • When using Intermittent as a Reproducibility, it is imperative that you state how many times a bug has occurred out of how many attempts to reproduce – “X out of Y”
  • Seen Once:
    • The bug has only occurred on a single occasion and has not yet been reproduced. This could be because you have not yet figured out exactly how to reproduce the bug despite your best kung fu, but the time has come to enter the bug and so “Seen Once”, although not preferred, is an acceptable selection


Element #4:
Steps to Reproduce

Just like it sounds, these are the exact necessary steps that anyone should follow to be able to reproduce the bug at will. Begin with any bug-specific setup information like “Using Windows98 SE:”, then number your steps.

Each step should contain a single action that the user is to perform – only ONE. When the next action is called for, that is another, separate step. Write each step necessary up to the point where the bug occurs. DO NOT write the bug in this sequence, only the steps!

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

Return To Successful Quality Assurance Home