Exploratory Testing Test Charters and Missions 2

Question 1

How should a tester handle a charter that turns out to be too broad for a single session?

Accepted Answer

Split it into multiple focused charters covering different aspects of the original scope

Answer

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'?

Accepted Answer

A charter designed to explore high-risk areas or functions most likely to contain defects

Answer

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?

Accepted Answer

Explore the checkout workflow with a guest user account to discover payment validation weaknesses

Answer

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?

Accepted Answer

It provides direction, prevents aimless testing, and enables tracking of coverage

Answer

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?

Accepted Answer

By mapping each charter to product features or user stories, teams can report which areas have been explored

Answer

Charters provide a lightweight unit of coverage that can be mapped to features or risks, giving stakeholders visibility into exploratory testing effort.

Exploratory Testing Practice Test

Exploratory Testing Practice Test

Exploratory Testing Test Charters and Missions 2