| |
10 Critical Elements of a Bug:
Day #3
Go To: Day 1 - Day 2 - Day 3 - Day 4 - Day 5 - Day 6 - Day 7This is the bug. The Result is the event that you experienced or witnessed that got you to stop testing and open up your bugbase.
Element #5:
Result
The event, the occurrence, the anomaly, the "wrong-thing-that-happened"...the Result is the bug. Whatever happened that made you raise an eyebrow, or sigh, or laugh hysterically; the Result is the defect that you are about to write.Something like: “Program crashed”. Then add the information that is needed to truly understand the bug, because as clear as “Program crashed” is, more information is needed. - Is the computer still in a usable state?
- Did the computer reboot?
- Did an error screen appear?
- What happened when the program crashed?
So add information like: “Mouse and keyboard no longer responsive. User has to reboot computer.”
Element #6:
Expected Result
This is what should have happened. Often this is simply the opposite of what did happen, but it needs to be explicitly called out so that there is a clear understanding of whether or not the expected behavior is accurate.This is the place to quote the specs that your test cases were based on. Something like: “Program should open the Help menu (per page 6, section 4.1 of tech doc #1.8.6v1)” Go To: Day 1 - Day 2 - Day 3 - Day 4 - Day 5 - Day 6 - Day 7Return To Successful Quality Assurance Home
|
