Chartr: give every session a clear mission

A test charter sets the direction for an exploratory session without turning it into a script. Chartr gives each charter the same structure, with guidance alongside on what makes a good one, so sessions stay purposeful and results are easy to compare.

Chartr showing two test charters with mission, scope, focus areas, resources and expected outcome, next to a guide to writing charters

What Chartr does

Mission
What you are investigating and what you want to learn.
Scope
The system area, environment and constraints for the session.
Focus areas
The quality risks and behaviours worth probing.
Resources
The data, tools, personas and dependencies you need.
Expected outcome
The signals that tell you the session gave useful coverage.
Built-in guidance
What a charter is, how to structure one and heuristics for writing a good one, next to the editor.

Why it matters

  • Charters stop sessions wandering, create a shared understanding and make results comparable across testers.
  • When risks change you update a charter, not dozens of rigid test cases.

Good to know

  • A charter guides a session. It does not replace the tester’s judgement about where to look next.

Questions

What is a test charter?

A short, focused mission for an exploratory testing session: what to explore, why now, and what evidence will make you confident.

Can I keep several charters in one session file?

Yes. Charters are listed together, and each can be cleared or deleted on its own.

Also in Holstr

Bring your next test session into one place

Get Holstr, or book a demo and see the whole workspace in action.