Exploratory Testing Charter Writing and Design

Question 1

What is the best way to phrase an exploratory test charter?

Accepted Answer

Explore [area] with [resources] to discover [information]

Answer

Execute test case TC-001 through TC-050

Answer

Verify that all requirements are met

Answer

Test the application until no bugs are found

Question 2

Which of the following is the BEST source of information for writing exploratory test charters?

Accepted Answer

Product requirements, risk analysis, and stakeholder input

Answer

Only the developer's source code

Answer

Previous automated test results alone

Answer

The bug tracker history exclusively

Question 3

How detailed should an exploratory test charter typically be?

Accepted Answer

Brief enough to allow freedom but specific enough to guide focus

Answer

Detailed enough to replace a test script

Answer

As vague as possible to allow maximum creativity

Answer

Detailed to the point of listing every step

Question 4

What risk does a poorly written charter pose to exploratory testing?

Accepted Answer

It may cause the tester to lose focus or duplicate effort already done

Answer

It automatically increases the number of bugs found

Answer

It forces the tester to write more session sheets

Answer

It triggers a mandatory test case review

Question 5

Which of the following is an example of a well-written test charter area?

Accepted Answer

Explore the checkout flow with a new user account to discover payment errors

Answer

Test everything in the application

Answer

Verify that the login page works

Answer

Check all buttons on all pages

Question 6

When is it appropriate to modify a charter mid-session?

Accepted Answer

When the tester discovers something more important or urgent to explore

Answer

Never — charters must be strictly followed

Answer

Only with written approval from the test manager

Answer

Only when no bugs have been found after 30 minutes