Why this matters
Scripted test cases check what the team expected. Real users do things nobody expected. Exploratory testing is how testers find those surprises: you learn the product, design tests and run them all at the same time, using your judgement as you go. It is a skill employers value and one you can practise on any device with any app.
Exploring is not wandering
Good exploratory testing has structure. Testers often work in short sessions with three parts:
- A charter: a one line mission that says what to explore and what to look for. For example: "Explore paying a bill with a weak network to discover how the app handles interruptions."
- A time box: a fixed period, usually 30 to 90 minutes, so you stay focused.
- Notes: a running record of what you tried, what you noticed, questions that came up and bugs found.
At the end you have evidence of what was covered, not just a vague feeling that you "had a look".
Ideas to guide your exploring
When you are not sure what to try next, use prompts like these:
- Interruptions: take a call, switch apps, lock the screen, turn data off and on, rotate the device.
- Going back: press back or refresh halfway through a payment or a form.