Bug reporting is central to testing. The bug report, whether oral or written, is the single most visible outcome of testing. And the quality of your reports is probably the single most important factor that determines your credibility as a tester. This document describes bug reporting from the perspective of Rapid Software Testing methodology. Throughout this guide I will distinguish between what is expected of “supporting testers” (anyone helping the test effort temporarily or intermittently but not committed to the testing role or perhaps even that project) and “responsible testers” (those who assume the role of tester on a project and commit themselves to doing that job well over time).