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 regression charter focused on known bugs

Answer

A performance charter focused on load testing

Answer

A security charter focused on SQL injection

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

A charter written to satisfy audit requirements

Answer

A charter that lists all known bugs to retest

Answer

A charter approved by the risk management team

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

Test data accounts

Answer

Browser versions to use

Answer

Environment and tools needed

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

It removes the tester's responsibility for finding defects

Answer

It guarantees 100% code coverage

Answer

It replaces the need for a formal test plan

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

Continue testing everything in the charter regardless

Answer

Abandon the session and start a new one

Answer

Request a new application build

Question 6

What does 'setup' refer to in the context of a test charter?

Accepted Answer

Prerequisites and environmental conditions needed before exploration begins

Answer

The test cases to be executed

Answer

The expected results for each action

Answer

The defect severity classification