Skip to content
← All CTFL glossary terms

Error guessing

An experience-based technique that anticipates likely errors, defects, and failures based on the tester's knowledge and past experience.

Syllabus chapters: 4

Sources: ISTQB® Certified Tester Foundation Level syllabus 4.0.1 and the official ISTQB® Glossary. Glossary content © International Software Testing Qualifications Board; source: glossary.istqb.org.

Related terms

Error guessing in a practice question

Question 1

A tester lists common mistakes developers make with date handling (leap years, time zones, end of month) and designs tests to attack each of them. Which technique is being used?

  1. Boundary value analysis
  2. Error guessing
  3. State transition testing
  4. Decision table testing
Show answer
  • Boundary value analysisBVA tests partition boundaries, not anticipated developer mistakes.
  • Correct answer: Error guessingAnticipating likely mistakes from experience and attacking them is error guessing.
  • State transition testingState transition testing models states and events, not guessed error types.
  • Decision table testingDecision table testing covers condition combinations, not experience-based guesses.

Error guessing anticipates errors, defects, and failures based on the tester's experience and knowledge of common developer mistakes. Listing likely error types and designing tests to expose them is a structured form called a fault attack.

Syllabus section 4.4.1

Question 2

A tester reviews how this application failed before, the errors its developers tend to make, and failures seen in similar products. How should this information be used in error guessing?

  1. Convert the information into acceptance criteria that direct implementation
  2. Use it only to select test conditions from an existing checklist
  3. Use it to calculate structural coverage of the implemented code
  4. Predict likely errors, defects, and failures, then design tests that expose them
Show answer
  • Convert the information into acceptance criteria that direct implementationAcceptance criteria confirm a user story; they are not how error guessing uses experience.
  • Use it only to select test conditions from an existing checklistChecklist-based testing covers listed test conditions but does not explain error guessing.
  • Use it to calculate structural coverage of the implemented codeStructural coverage belongs to white-box testing and is not derived from this experience.
  • Correct answer: Predict likely errors, defects, and failures, then design tests that expose themExperience supports predictions, and tests are designed to expose the predicted defects or failures.

Error guessing uses the tester's knowledge of past application behavior, developers' typical errors and resulting defects, and failures in similar applications to predict errors, defects, and failures and design tests that expose them. A fault attack can implement this by using a corresponding list.

Syllabus section 4.4.1

Original PrepBench practice material, not official exam questions or exam dumps. PrepBench is independent and is not affiliated with or endorsed by ISTQB®.