From the course: Software Testing Foundations: Bug Writing and Management

Unlock the full course today

Join today to access over 24,900 courses taught by industry experts.

What makes a good bug

What makes a good bug

- [Instructor] There are good bugs and bad bugs. We aren't talking about the nature of the issue, or even its severity. We are discussing the value and importance of delivering a well-written, beautifully composed, and ready to share bug. This is what developers consider a good bug, because it means they can take it and fix it. Understanding what makes a good bug is about looking at your role in reporting issues and how you can make the developer not only understand the problem, but appreciate your role in sharing it. You see, developers don't like bugs. In fact, there are a few people who do. However, when one is discovered, it's the job of the tester to report it. Doing this well rewards both you and those who read it. Let's begin by recognizing that we aren't all writers, and that you don't need to be an author to deliver a good bug. It starts with clarity and grammar. People are reading your issues, and it's essential they understand what you wrote. There is no need to pull out a…

Contents