Exploratory Testing Test Charters and Missions 2 — Questions and Answers
Question 1: How should a tester handle a charter that turns out to be too broad for a single session?
- Split it into multiple focused charters covering different aspects of the original scope (Correct answer)
- Complete as much as possible and mark the rest as skipped
- Request a longer session duration to cover all areas
- Abandon the charter and create a scripted test suite instead
Correct answer: Split it into multiple focused charters covering different aspects of the original scope
A broad charter should be broken into smaller, focused charters so each session has a manageable and meaningful scope.
Question 2: What is a 'risk-based charter'?
- A charter designed to explore high-risk areas or functions most likely to contain defects (Correct answer)
- A charter used only during security penetration testing
- A charter that documents all risks found after a session completes
- A charter written by risk management stakeholders, not testers
Correct answer: A charter designed to explore high-risk areas or functions most likely to contain defects
Risk-based charters target areas where failures would have the greatest impact or where defects are most likely to exist based on complexity or change history.
Question 3: Which of the following best represents a well-written exploratory test charter?
- Explore the checkout workflow with a guest user account to discover payment validation weaknesses (Correct answer)
- Click the Buy Now button and verify the confirmation email is received
- Test the payment module — check all fields
- Verify that the shopping cart correctly calculates totals
Correct answer: Explore the checkout workflow with a guest user account to discover payment validation weaknesses
A well-written charter is specific about the target (checkout workflow), the resource (guest user account), and the goal (payment validation weaknesses).
Question 4: What is the benefit of writing charters before starting an exploratory testing session?
- It provides direction, prevents aimless testing, and enables tracking of coverage (Correct answer)
- It guarantees full test coverage of all features
- It eliminates the need for debriefs after sessions
- It converts exploratory testing into scripted testing for auditability
Correct answer: It provides direction, prevents aimless testing, and enables tracking of coverage
Pre-written charters ensure testers have a clear purpose before they start, preventing unstructured exploration that lacks accountability.
Question 5: How do test charters support test coverage reporting in agile projects?
- By mapping each charter to product features or user stories, teams can report which areas have been explored (Correct answer)
- By generating automated coverage reports from the test management tool
- By requiring testers to write one charter for every acceptance criterion
- By linking charters to code commits tracked in the CI/CD pipeline
Correct answer: By mapping each charter to product features or user stories, teams can report which areas have been explored
Charters provide a lightweight unit of coverage that can be mapped to features or risks, giving stakeholders visibility into exploratory testing effort.
Question 6: What is the role of 'product areas' in test charter design?
- They define the scope boundaries of the charter to ensure focused, manageable exploration (Correct answer)
- They determine which automation framework to use for the session
- They specify the exact test data required before the session begins
- They list the developers responsible for each feature under test
Correct answer: They define the scope boundaries of the charter to ensure focused, manageable exploration
Defining product areas in a charter scopes the exploration to a specific part of the system, preventing scope creep during the session.
Exploratory Testing Test Charters and Missions 2
How should a tester handle a charter that turns out to be too broad for a single session?