Part 3 "Bonus Program" Applying exploratory testing (ET) during unit testing is being considered. Which ET deliverable would be the primary candidate for informal reviews? 1 credit [K2]

Question

Options

• ATest log & coverage outline
• BTest charter
• CHeuristics
• DTest case specification

• A
  7% (2)
• B
  90% (26)
• D
  3% (1)

Explanation

A test charter is the defining artifact of an exploratory testing session - it captures the mission, scope, and goals of what to explore and why, making it naturally suited for a quick, informal peer review before or during the session. It is concise, lightweight, and written to guide a tester's intent rather than prescribe rigid steps, which is exactly what informal review targets.

Why the distractors are wrong:

• A (Test log & coverage outline): These are outputs recorded after testing occurs - they document what happened, not what to do, so they serve reporting purposes rather than pre-session review.
• C (Heuristics): Heuristics are general mental frameworks or rules of thumb (e.g., SFDIPOT) that guide a tester's thinking; they are not session-specific deliverables and aren't reviewed in context the way a charter is.
• D (Test case specification): This is a formal, scripted testing artifact - the opposite of exploratory testing's lightweight nature - and would call for formal rather than informal review.

Memory tip: Think "charter = mission brief." Just like a quick team huddle before a mission, a test charter is short enough to review informally in minutes - it tells what to explore and why, making it the ideal candidate for a lightweight review before the session begins.

No community discussion yet for this question.