CTFL 4.4.2: Explain exploratory testing

• a
  When detailed, stable specifications exist and regulatory evidence of coverage is requiredDetailed specs and required coverage evidence favor scripted, not exploratory, testing.
• ✓
  Correct answer: When specifications are sparse and there is significant time pressureSparse specifications and time pressure are exactly where exploratory testing adds most value.
• c
  When the same checks must be repeated identically on every releaseIdentical repeated checks suit automated scripted regression, not exploratory testing.
• d
  When tests must be derived mechanically from a decision tableMechanical derivation describes a black-box technique, not exploratory testing.

Exploratory testing — simultaneously learning, designing, and executing tests — is most useful when specifications are missing or inadequate, under time pressure, or as a complement to formal techniques. Session-based testing can give it structure.

Syllabus section 4.4.2

• a
  The tester executes fixed test conditions from a prepared checklist without changing directionThis describes checklist-based testing rather than adapting tests while learning.
• b
  The tester derives all tests before execution from a list of possible errors and failuresThis describes a fault attack, a way to implement error guessing.
• ✓
  Correct answer: The tester designs, executes, and evaluates tests while learning about the test objectExploratory testing combines design, execution, evaluation, and learning.
• d
  The team writes acceptance tests before implementation to direct developmentThis describes acceptance test-driven development, not exploratory testing.

In exploratory testing, tests are simultaneously designed, executed, and evaluated while the tester learns about the test object. Learning is used to explore more thoroughly with focused tests and to create further tests for untested areas, which is useful when specifications are scarce or time pressure is high.

Syllabus section 4.4.2

• a
  It is checklist-based testing, and the document is the checklist of conditions to coverChecklist-based testing covers test conditions from a checklist, and the tests are not designed while learning.
• b
  It is error guessing, and the document lists the errors the developers are likely to makeError guessing anticipates errors, defects and failures from the tester's knowledge, not within a timed session.
• ✓
  Correct answer: It is session-based exploratory testing, and the document is a test charter that guides itTime box, charter with objectives, session sheet and debriefing are the session-based approach.
• d
  It is scripted black-box testing, and the document fixes the test cases before the sessionScripted testing fixes test cases in advance, whereas here design and execution happen together.

In exploratory testing, tests are simultaneously designed, executed and evaluated while the tester learns about the test object. It is sometimes performed as session-based testing: the testing runs within a defined time box, the tester uses a test charter containing test objectives to guide it, session sheets document the steps followed and the discoveries made, and the session is usually followed by a debriefing with stakeholders interested in the results.

Syllabus section 4.4.2