A test charter is a concise mission statement for an exploratory testing session. It defines what to explore, the resource or data to use, and the information to discover, keeping attention on a specific risk. section 8.1 section 8.1.2
Build and use charters through a risk-focused sequence:
- Identify a product or functional risk. section 8.1
- Convert the risk into a focused exploration mission. section 8.1.2
- Prioritize charters by risk, track which risks have been explored, and assess the value of each session. section 8.1
- Use tester judgment to identify risks, because generating them remains heuristic rather than procedural. section 8.1
Explore <target> With <resource> To discover <information>
Use the compact pattern “Explore <target> with <resource> to discover <information>” to make a charter’s scope and purpose explicit. section 8.1
From risk to charter
Risk: bookings are not shown in the report view. Charter: explore how bookings are rendered in the report view with a collection of bookings to discover if all bookings are shown correctly. Variants can use very large collections, different personas, malformed data, or proxy tools to examine readability, understandability, and error handling. section 8.1.2
