Pathwise

Manuals / Exploratory Testing / Chapter 2

A · Structure · beginner · Week 1 · Chapter 2 of 9

Charters that focus freedom

A charter says where to explore and why — not step-by-step scripts. Too vague = wandering. Too tight = scripted testing in disguise.

Path progress
22%

Step 1 of 1

Write charters

Explore <target> with <resources> to discover <information>.

Write chartersDrag stickies · tap for tips
Study mapDrag stickies · tap for tipsKeep it shortdrag · tap →Name the waitdrag · tap →Scope locatorsdrag · tap →Trace when stuckdrag · tap →One browser firstdrag · tap →Isolate statedrag · tap →Assert the UIdrag · tap →Retry wiselydrag · tap →Seed datadrag · tap →Close the loopdrag · tap →Keep it shortdrag · tap →Name the waitdrag · tap →Scope locatorsdrag · tap →Trace when stuckdrag · tap →One browser firstdrag · tap →Isolate statedrag · tap →Pathwise hackdrag · tap →Write chartersdrag · tap →Try thisdrag · tap →Follow the dashed drag · tap →

Example

Explore checkout with invalid coupons and currency changes
to discover price calculation and error-handling risks.

Explore settings permissions as a new user
to discover authorization gaps and confusing defaults.

Do this now

Write 5 charters for your app. Star the two you’ll run this week.

Pro tip: Include a risk or question. “Explore the app” is not a charter.

Was this step clear?
Chapter learning outcomes
  • Charter format
  • Scope & risks
  • Good vs mushy

Clear these before you leave