Exploratory Testing Charter Writing and Design 2

Question 1

What type of charter would be most useful at the start of testing an unfamiliar application?

Accepted Answer

A reconnaissance charter focused on understanding the system

Answer

A reconnaissance charter helps testers build a mental model of the system before diving into specific risk areas.

Question 2

What is a 'risk-based charter' in exploratory testing?

Accepted Answer

A charter targeting areas most likely to have high-impact defects

Answer

Risk-based charters focus testing effort on areas with the highest potential impact if defects are present.

Question 3

Which of the following would NOT typically appear in the 'resources' portion of a charter?

Accepted Answer

The expected number of bugs to find

Answer

The expected bug count is not a resource — resources refer to tools, accounts, data, and environments needed for testing.

Question 4

What is the benefit of creating charters collaboratively with developers or product managers?

Accepted Answer

It ensures charters reflect product knowledge and risk areas the team values

Answer

Collaborative charter creation surfaces domain knowledge and ensures testing aligns with the team's most critical concerns.

Question 5

How should a tester handle a charter that proves too broad during a session?

Accepted Answer

Note the scope issue, narrow the focus, and suggest splitting into multiple charters

Answer

When a charter is too broad, the tester should narrow focus mid-session and recommend splitting it for future sessions.

Exploratory Testing Practice Test