Module 7: Exploratory Charters for Complex Logic

Sometimes there is no decision table to fill in. No state diagram to trace. The specification was written three years ago, never updated, and bears almost no resemblance to what was actually built. Or perhaps it was never written at all.

This is when exploratory testing stops being a fallback strategy and becomes the primary tool. But "explore" does not mean "click around randomly." Structured exploration — through sessions with explicit charters, time boxes, and debrief protocols — is a disciplined professional practice.

Lessons in this module

1. Session-Based Exploratory Testing — The SBET framework: what a session is, how time-boxing works, what the charter-tour-debrief cycle looks like. Understand why structure and freedom are not opposites.
2. Writing an Exploratory Charter — The anatomy of a charter: Mission (what to explore), Area (where to explore), and Risks (what could go wrong). Learn to write charters that are focused but not rigid.
3. Debriefing — What to Report and How — The three categories of session notes: bugs found, issues observed, test coverage achieved. How to produce a debrief that is useful for stakeholders, not just for yourself.
4. Charters for Hidden Business Logic — How to reverse-engineer rules from system behavior when no specification exists. The probe-observe-model cycle: form a hypothesis, test it, update your mental model.

No Practice Challenge This Module

Module 7 is deliberately practice-free. The skills you have built across this course — decision tables, cause-effect graphs, boolean analysis, state transitions, pairwise selection, error guessing — are your toolkit. Exploratory testing is how you wield them when there is no challenge specification to hand you.

By the end of this module, you will earn the Charter Navigator badge.