Skip to content
← All CTFL glossary terms

Decision table testing

A black-box technique that models combinations of conditions and resulting actions in a table, with each column forming a test case.

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

Decision table testing in a practice question

Question 1

A loan application system evaluates three conditions: Condition 1: the applicant is an existing customer. Condition 2: the applicant's credit score is above 700. Condition 3: the applicant requests more than 50,000. Any combination in which the applicant is not an existing customer and requests more than 50,000 is infeasible, because only existing customers may request that amount. The full decision table covers every combination of the three conditions. After the infeasible columns are deleted, how many columns remain to be exercised?

  1. 4
  2. 5
  3. 6
  4. 8
Show answer
  • 4This would delete four columns; only the two with Condition 1 false and Condition 3 true are infeasible.
  • 5This deletes three columns, but Condition 2 is free in only two of them.
  • Correct answer: 68 full columns minus the 2 infeasible ones leaves 6 feasible columns.
  • 88 is the size of the full table before the infeasible columns are deleted.

A full decision table has enough columns to cover every combination of conditions, so three Boolean conditions give 2 x 2 x 2 = 8 columns. The infeasible combination fixes Condition 1 as false and Condition 3 as true, while Condition 2 remains free, which describes 2 of those columns. Deleting them leaves 6 feasible columns, and in decision table testing the coverage items are exactly the columns containing feasible combinations.

Syllabus section 4.2.3

Question 2

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

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