LESSON VIEW
PQA-05 · LEVEL 2 PRACTITIONER · PRACTICAL QA

Charters, Sessions and Notes That Become Evidence

Objective: Run disciplined exploratory testing: a five-line charter that aims the work, one time-boxed uninterrupted session, and timestamped notes that separate observations, questions and issues well enough to survive a debrief.

⏱ ≈90 min full lesson · Includes a 30-minute practice session · English edition — Español · العربية · বাংলা in translation

🧽 The practice business: FreshNest Home Cleaning — a fictional local cleaning company (owner: Maya Torres) invented for this course. Every example and exercise uses FreshNest, so you learn on a complete, realistic business without ever touching a real one.

⚡ Key Points

  • A charter is a mission, not a script: target, risk, oracles, boundaries — a few lines.
  • The timebox (45–90 min, uninterrupted) is what makes coverage reportable.
  • Notes are the product: timestamped, or the session evaporates.
  • Separate three kinds of sentences: observations, questions, issues.
  • An issue cites the oracle it violates — 'wrong against REQ-FN-01', not 'looked off'.
  • Explore to discover; script to protect. Each mode finds what the other misses.

📖 Read

Scripted tests answer questions you already knew to ask. Exploratory testing exists for the other kind — the problems nobody predicted. It is not the opposite of disciplined testing; done properly it is the most disciplined testing there is, because the tester designs, executes and evaluates at the same time, and then has to prove what they covered.

The unit of work is the charter: a mission statement, not a script. A good charter names the target area, the risk or question driving the session, the oracles to check against, and the boundaries — a few lines whose job is to aim the session, not choreograph it. Work happens in time-boxed, uninterrupted sessions, and the timebox is what makes coverage reportable: 'in 60 minutes I covered Standard and Deep across all bedroom counts; the date picker was not touched' is information a manager can act on.

Notes are the product. Exploration evaporates unless the notes become evidence: timestamped entries that separate observations (what the system did), questions (what you don't know yet), and issues (what looks wrong, with the oracle it violates). Mixed into one stream of consciousness they cannot be checked or defended; separated, they survive a debrief. The trade-off is exploration versus repeatability — so mature teams explore to discover, then convert valuable findings into scripted checks to protect. And the misconception to drop: exploratory testing is not random clicking. No charter, no timebox, no evidence, no debrief means it wasn't exploration; it was wandering.