Thinking Like a Tester
A developer looks at a feature and thinks "how do I make this work?" A tester looks at the same feature and thinks "how might this break?" Both perspectives are essential. Neither is more important. But they're fundamentally different modes of thinking.
The Skeptical Mindset
Good testers are professional skeptics. Not cynics — skeptics. The difference matters. A cynic says "this will never work." A skeptic says "let me verify that this actually works the way we think it does."
When someone says "the login works," a tester's brain automatically generates questions:
- Works with what credentials?
- Works on which browsers?
- Works when the database is slow?
- Works when two people log in simultaneously?
- Works when the session cookie is tampered with?
This isn't negativity. It's thoroughness.
Cognitive Biases That Hurt Testing
Testers need to fight their own biases:
Confirmation bias: You test to confirm the software works, not to find where it fails. Fix: actively try to break things. If you think a feature works, try to prove yourself wrong.
Anchoring: The first bug you find shapes how you look at the rest of the feature. Fix: reset your perspective. After finding a UI bug, deliberately switch to testing the backend.
Automation bias: "The automated tests passed, so it's fine." Fix: automated checks can only find the bugs they were designed to catch. Explore beyond the scripts.
Asking Better Questions
The most powerful tool in a tester's toolkit isn't a framework or a script. It's the question "what if?"
- What if the network drops mid-transaction?
- What if a user enters emoji in the name field?
- What if the clock changes during a timed operation?
- What if the user is on a 3G connection?
- What if the database returns an empty result?
Every "what if" is a potential test case. The best testers generate these instinctively, across every layer of the system.
Practice: The Observation Game
Next time you use any app, spend 5 minutes with the tester mindset. Don't use it normally — observe it. Notice things:
- What happens when you tap rapidly?
- Are error messages helpful or generic?
- Does the back button work from every screen?
- What happens when you rotate your phone mid-action?
You'll start noticing things you never saw before. That's the testing mindset clicking on.
The key takeaway: Testers don't just find bugs — they find the assumptions nobody questioned.
A developer says "the login works." Which response best demonstrates the testing mindset?
The testing mindset generates "what if" questions that challenge assumptions. Rather than accepting a vague claim or running a single check, a skilled tester probes the boundaries of what "works" actually means.
What is confirmation bias in testing, and how do you counter it?
Click to reveal answer
Confirmation bias is the tendency to test in ways that confirm the software works rather than trying to find failures. Counter it by actively trying to break things — if you think a feature works, deliberately try to prove yourself wrong.
Click to flip back
Which cognitive bias is at play when you say "the automated tests passed, so the feature is fine"?
Automation bias is the tendency to over-trust automated results. Automated checks can only find bugs they were designed to catch. Passing automated tests don't guarantee the absence of bugs in untested scenarios.