Q25 of 38 · Test design

What is an exploratory test charter and what does one contain?

Test designJuniortest-designexploratory-testingchartersession-based-testing

Short answer

Short answer: A charter is a short, focused brief for an exploratory testing session. It defines what to explore, what information to gather, and optionally a time-box. It gives structure to exploration without scripting every step.

Detail

A well-formed charter follows the pattern: Explore [target area] using [resources/tools] to discover [information/risks].

For example: "Explore the password reset flow using expired tokens and concurrent reset requests to discover whether the token is properly invalidated after first use."

A charter scopes the session without prescribing steps — the tester's judgement drives the actual actions. After the session the tester reports findings, bugs, questions, and coverage notes. This structured record makes exploratory testing auditable and repeatable across sprints.

Charters are particularly useful during a new feature's first testing cycle, after a major refactor, or when a risk area is too complex to enumerate in test cases beforehand.

// WHAT INTERVIEWERS LOOK FOR

The Explore/Using/To Discover structure. Knowing charters scope without scripting. Understanding that output is a session report, not just a pass/fail.

// Related questions

When do you choose exploratory testing over scripted test cases, and how do you make the output auditable?

Test design