When testers are successful, they will come across bug symptoms. This section explains the fine art of bug isolation – turning a symptom into a well-defined bug report. Also, the organizational factors that need to be considered in order to maximize the chance of getting the bug fixed.
a. "A problem well-stated is half-solved."
b. The Goal of Bug Reporting
c. The Importance of Reproducibility
d. Isolation and Simplification
i. Bottom-up
ii. Top-down
iii. The “binary defect search” technique
e. Generalization
f. Bug Reporting
i. Important Elements
ii. Working with Developers
iii. Follow-up
No comments:
Post a Comment