Module 2 · Testing fundamentals
Exploratory testing and risk-based priorities
Structured exploration with charters, and ranking what to test by likelihood and impact.
About 10 min reading and 20 min practice (estimates)
Loading progress…
Read
Learning objectives
- Write a focused exploratory testing charter.
- Take useful notes during a time-boxed session.
- Prioritise test areas using likelihood and impact.
Explanation
Exploratory testing means designing and running tests at the same time, using what you learn to decide what to try next. It is not random clicking: a good session has a charter (a mission), a time box (often 45–90 minutes) and notes.
Explore <target>
with <resources, data or techniques>
to discover <information>Risk-based prioritisation
You can never test everything, so decide where problems are most likely and would hurt most. Score each area for likelihood (complex logic, recent changes, history of bugs) and impact (money, data, legal exposure, number of users affected). Test the high–high areas first and deepest; note what you consciously test lightly.
| Low impact | High impact | |
|---|---|---|
| High likelihood | Test, moderate depth | Test first, in depth |
| Low likelihood | Light check or accept the risk | Targeted checks |
Example: a charter for the training shop's cart
Charter: Explore the Dar Al Souq cart
with quantity changes, removals and both promotion codes
to discover whether the order summary always matches the lines.
Time box: 45 minutes
Notes (excerpt)
10:05 2 items, qty 1 each, summary OK
10:12 Raised qty to 3 → line and summary both updated
10:20 Question: is the code kept after removing every eligible item?
10:31 Possible issue → reproduce, then reportCommon mistakes
- Exploring without a charter and losing focus.
- Not taking notes, so a problem can't be reproduced later.
- Ranking risks by personal interest instead of likelihood and impact.
- Treating low-priority areas as "tested" when they were skipped.
Try
Practise what you just read. Answers are checked here; nothing is graded publicly or counts toward Bug Arena.
Exercise
Open Bug Arena Practice and run a 20-minute exploratory session on the training shop. Write your charter first, then three notes: what you tried, what you observed, and one question to follow up.
Write your answer first, then compare it with the sample solution. It stays on this page only and isn't sent anywhere.
Review
Check yourself — you should now be able to:
- Write a focused exploratory testing charter.
- Take useful notes during a time-boxed session.
- Prioritise test areas using likelihood and impact.
Practise in QA Lab
References
Continue
When you’re ready, mark the lesson complete in the Try step and move on.
Marked as read when you reach the end of the lesson.