liveBook · Manning

Bug

As explained in Bug Bash

A defect in software that causes incorrect, unexpected, undesirable, or insecure behavior.

A bug is a software error, defect, or feature that does not work as expected or intended. It can make a product behave incorrectly, unexpectedly, undesirably, or insecurely. Bugs are not always obvious to the people who built or repeatedly tested the product: familiarity can make teams overlook problems or miss ways that other people use it. section 1.0 section 1.2.1

Finding bugs before release matters because fewer production problems can make a product better and less costly for the organization. A bug bash concentrates feedback and discovery into a short period before a milestone, helping teams surface unexpected issues and improve delivery. section 1.2.1

Different people help reveal different bugs because they bring distinct roles, needs, experiences, and perspectives:

  • People who are new to a product may notice an issue that experienced team members have come to accept. section 1.2.1
  • People’s cultural backgrounds, age, hobbies, and other personal factors can affect how they test and what they notice. section 1.2.1
  • Reported bugs can range from improvement suggestions to urgent or critical issues, including concerns involving user experience and security. section 1.3

A name that prevented login

A website allowed sign-in with a Google Account but crashed for a user whose Lithuanian surname contained “ė.” The system handled only names using English alphabet characters. What seemed like a small assumption could have made the site unusable for millions of users. section 1.2.1

Figure 1.2 In a bug bash, we bring more than our roles: we bring who we are as people, and each of us has a unique combination. Various factors, such as age, cultural background, or even hobbies, affect how we test and which bugs we notice.

Personal characteristics as well as job roles shape the paths people take through a product and the bugs they are able to spot. section 1.2.1

A large number of reported bugs is useful feedback rather than automatic failure. In a bug bash, even a small company may collect more than 100 reports in 2.5 hours, often including critical problems discovered before release. section 1.3

How Bug Bash covers it

How deep it goes
Defines bugs plainly and explains why diverse testers uncover overlooked issues, without detailing technical root-cause analysis or fixes.
Examples
Illustrates a login crash caused by a Lithuanian surname containing “ė” and reports companies finding over 100 bugs in 2.5 hours.
What it assumes
Introduces the meaning of a bug from zero and does not require professional testing expertise.
What you can do after
Evaluate/understand why involving people with varied perspectives can expose bugs before release.
How it connects
Connects bugs with bug bashes, testing, feedback, user experience, security, and product release.

Also explained in

Compare how 5 books explain bug →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Bug Bash. The section links point to the parts of the book it draws on.