Exploratory Testing Test Charters and Missions 1 — Questions and Answers
Question 1: What is a test charter in exploratory testing?
- A brief statement that defines the scope, target, and purpose of an exploratory test session (Correct answer)
- A detailed scripted test plan with expected results
- A legal document authorizing the tester to access the system under test
- A report summarizing bugs found during a test cycle
Correct answer: A brief statement that defines the scope, target, and purpose of an exploratory test session
A test charter provides direction for an exploratory session by specifying what to explore, the product area to focus on, and the goal or information to gather.
Question 2: Which of the following is the most effective format for writing a test charter?
- Explore [target] with [resources] to discover [information] (Correct answer)
- Test case ID: Step 1, Step 2, Expected Result
- Feature name, preconditions, test data, and expected outcome
- User story with acceptance criteria and story points
Correct answer: Explore [target] with [resources] to discover [information]
The 'Explore / with / to discover' format gives a charter enough direction to guide testing while leaving room for the tester to investigate freely.
Question 3: What is the key difference between a test charter and a scripted test case?
- A charter defines intent and scope while a scripted test case prescribes exact steps and expected results (Correct answer)
- A charter is used only for automated testing while a scripted test case is for manual testing
- A charter requires management approval while a scripted test case does not
- A charter covers non-functional testing only while a scripted test case covers functional testing
Correct answer: A charter defines intent and scope while a scripted test case prescribes exact steps and expected results
A charter empowers the tester to decide how to explore, while a scripted test case dictates every action the tester must take.
Question 4: Who is responsible for writing test charters in an exploratory testing engagement?
- Charters can be written by testers, test leads, product owners, or anyone with knowledge of risks and requirements (Correct answer)
- Only senior test managers are authorized to write charters
- Developers write charters based on unit test failures
- Business analysts write all charters during requirements gathering
Correct answer: Charters can be written by testers, test leads, product owners, or anyone with knowledge of risks and requirements
Charters can be written by anyone with knowledge of the product's risks, making them a collaborative artifact in exploratory testing.
Question 5: What does a 'mission-based' test charter emphasize?
- A clear goal or information need that guides the tester's investigation (Correct answer)
- A strict sequence of test steps that must be followed
- The number of bugs the tester must find per session
- The specific tools and automation scripts the tester must use
Correct answer: A clear goal or information need that guides the tester's investigation
Mission-based charters keep testing purposeful by ensuring every session has a clear reason to exist and a tangible outcome to aim for.
Question 6: What is 'charter drift' in exploratory testing?
- When a tester deviates significantly from the original charter scope during a session (Correct answer)
- When a charter is updated mid-sprint to reflect new requirements
- When two testers accidentally cover the same charter simultaneously
- When a charter is poorly written and lacks a clear target
Correct answer: When a tester deviates significantly from the original charter scope during a session
Charter drift occurs when a tester's investigation wanders too far from the original charter, reducing accountability and coverage focus.
Exploratory Testing Test Charters and Missions 1
What is a test charter in exploratory testing?