Find the Bug Scenarios
Spot the defects in realistic QA scenarios.
A login form accepts an email and password. When the user submits an email without an "@" symbol, the form shows a spinner forever and no error message appears. The network tab shows a 400 response from the server.
List the bugs you can spot before revealing the answer.
About Find the Bug Scenarios
Find the Bug presents realistic QA scenarios — a login form, a shopping cart, a paginated API, a booking form — each hiding real defects. Write down everything you can find, then reveal the answer list and compare. It trains the observational skill that no tooling replaces: noticing what is wrong.
The scenarios reward systematic inspection over lucky guessing: broken calculations, off-by-one logic, missing validation, unhandled errors. Work through them like a real exploratory session and the habits transfer directly to your day job.
How to use
- Study the scenario carefully — assume nothing is accidental.
- List every defect you spot in "Your findings", as if reporting them.
- Click "Reveal bugs" and compare the official list with yours.
- Use "Copy my findings" to save your notes, then move on with Prev/Next.
Frequently asked questions
What if I find an issue that is not on the answer list?
That happens with good testers — scenarios can contain unintended defects, and defensible judgment calls differ. If you can articulate why it is a problem for a user, count it.
How is this different from a quiz?
Quizzes test knowledge; this tests observation. There are no options to choose from — like real testing, you first have to notice that something is wrong before you can name it.
How do I get better at spotting bugs?
Inspect systematically instead of scanning: check every boundary, every label against every behavior, every claim in the requirements against the artifact. Speed comes later; thoroughness is the trainable part.