Exploratory Testing Charter Writing and Design 1 — Questions and Answers
Question 1: What is the best way to phrase an exploratory test charter?
- Explore [area] with [resources] to discover [information] (Correct answer)
- Execute test case TC-001 through TC-050
- Verify that all requirements are met
- Test the application until no bugs are found
Correct answer: Explore [area] with [resources] to discover [information]
A charter is best written as 'Explore [area] with [resources] to discover [information]' to convey focus and intent.
Question 2: Which of the following is the BEST source of information for writing exploratory test charters?
- Product requirements, risk analysis, and stakeholder input (Correct answer)
- Only the developer's source code
- Previous automated test results alone
- The bug tracker history exclusively
Correct answer: Product requirements, risk analysis, and stakeholder input
Effective charters are derived from requirements, risks, and stakeholder input to ensure relevant coverage.
Question 3: How detailed should an exploratory test charter typically be?
- Brief enough to allow freedom but specific enough to guide focus (Correct answer)
- Detailed enough to replace a test script
- As vague as possible to allow maximum creativity
- Detailed to the point of listing every step
Correct answer: Brief enough to allow freedom but specific enough to guide focus
Charters strike a balance — they guide the tester's focus without eliminating the freedom to explore.
Question 4: What risk does a poorly written charter pose to exploratory testing?
- It may cause the tester to lose focus or duplicate effort already done (Correct answer)
- It automatically increases the number of bugs found
- It forces the tester to write more session sheets
- It triggers a mandatory test case review
Correct answer: It may cause the tester to lose focus or duplicate effort already done
A vague or poorly scoped charter can cause unfocused testing, wasted time, or overlap with other sessions.
Question 5: Which of the following is an example of a well-written test charter area?
- Explore the checkout flow with a new user account to discover payment errors (Correct answer)
- Test everything in the application
- Verify that the login page works
- Check all buttons on all pages
Correct answer: Explore the checkout flow with a new user account to discover payment errors
A good charter names a specific area, a context, and what kind of information to look for.
Question 6: When is it appropriate to modify a charter mid-session?
- When the tester discovers something more important or urgent to explore (Correct answer)
- Never — charters must be strictly followed
- Only with written approval from the test manager
- Only when no bugs have been found after 30 minutes
Correct answer: When the tester discovers something more important or urgent to explore
Exploratory testers can deviate from a charter when a discovery leads to a more important investigation.
What is the best way to phrase an exploratory test charter?