1 What’s a bug bash?
This chapter covers
- What a bug bash is and why it matters
- What is a high-level overview of a bug bash
- What you will need before running a bug bash
How many times have you—or worse yet, your customers—shouted at a piece of software: “How could you not have tested this?”
In a perfect world, every application, feature, or service would be thoroughly vetted by a dedicated team of professional software testers. In reality, however, testing can be expensive and time-consuming; not all companies have dedicated testing departments, and even if they do, there may be use cases that are overlooked.
A bug bash offers the benefits of utilizing existing resources (both within and outside a software development team). Additionally, it provides a valuable range of perspectives that may uncover insights that would be missed in typical software testing. We’ll take a closer look at how a bug bash works and show you how to get started.
1.1 What’s a bug bash?
Imagine a global software company called Bash IT. Their story is one many software companies know all too well, and one I’ll use to illustrate the concept throughout the book. It’s about dealing with… bugs.
A bug
is a software error, defect, or feature that does not function as expected or intended.