Think like a tester
The core skill of QA isn't a tool — it's a way of looking at software and asking 'what did they forget?' Let's build that instinct.
8 steps · 5 minTesting is prediction
A good tester doesn't just follow steps someone wrote down. They look at a feature and predict how it will break — before anyone clicks anything.
That instinct is learnable. This lesson trains it with a few real examples.
A simple login form
Picture a login screen: an email field, a password field, and a 'Log in' button. The developer built it for the obvious case — a real email and the right password.
Your job is to think about everything *other* than the obvious case.
You can only try one input first. Which is most likely to reveal a bug the developer forgot about?
These are "edge cases"
An edge case is an input or situation at the boundary of what the software expects: empty fields, huge values, weird characters, doing two things at once. Most real bugs live here.
Train yourself to ask: what's the strangest thing a real person could do here?
A shopping cart lets you set the quantity of an item. The developer was thinking '1, 2, 3...'. What's the sharpest edge case to try?
Finding the bug is half the job
The other half is reporting it so it actually gets fixed. A vague report gets ignored. A clear one gets a developer nodding and reaching for the code.
A good report has: what you did, what you expected, and what actually happened.
Which of these bug reports is a developer most likely to fix quickly?
That's the mindset
You just did the real work of QA: predict where software breaks, push on the edges, and report what you find clearly. Tools come later — this thinking is the foundation everything else is built on.
Next up in the pathway: what a QA engineer actually does all day.
Lesson complete.
You just practiced the real work of QA — predicting failure, probing the edges, and reporting clearly. That instinct is the foundation everything else builds on.