B · Thinking toolsIntermediate30 min read
6. Oracles & recognizing bugs
Exploratory Testing · 36 pages source format
An oracle is how you know something is wrong: consistency, standards, user expectations, history, claims in docs.
What you'll learn
- FEW HICCUPPS
- Consistency oracles
- When “weird” isn’t a bug
Name your oracle
Every bug report implies an oracle. Make it explicit.
Do this now
For 3 bugs you’ve filed (or will file), write the oracle in one line.
Pro tip. “I don’t like it” is taste. “Violates stated pricing rules” is an oracle.
Clear?