What is Decision Table Testing?
Decision table testing is a black-box test design technique that maps combinations of input conditions to expected actions in a table, ensuring every meaningful combination of conditions is tested systematically rather than by guesswork. It suits business rules with several interacting conditions, such as discount eligibility, where a plain list of cases misses combinations.
No account needed · Scored in under a minute against a senior rubric
What does Decision Table Testing mean in practice?
When behavior depends on several conditions interacting, ad-hoc testing easily misses combinations. A decision table makes them explicit: conditions are listed as rows at the top, each column is a unique combination (a "rule") of those conditions, and the resulting actions or outcomes are the rows at the bottom. With N boolean conditions there are up to 2^N combinations, and the table forces you to consider each.
For example, a discount might depend on "is a member?", "order over $100?", and "has a coupon?". A decision table lays out all eight combinations and the expected discount for each, immediately revealing combinations the developer (and the spec) may have overlooked. In practice you often collapse impossible or equivalent combinations to keep the table manageable.
Decision table testing pairs naturally with equivalence partitioning and boundary value analysis, and it is especially valuable for business-rules-heavy logic (pricing, eligibility, permissions). It is a staple of the ISTQB syllabus and a common interview technique question.
Why do interviewers ask about Decision Table Testing?
Decision table testing is a named test-design technique interviewers expect QA candidates to know. Describing how it systematically covers combinations of conditions, and when to use it (complex business rules), demonstrates structured test design.
What does Decision Table Testing look like in a real project?
A loan-approval feature depends on credit score, income, and existing debt. A decision table enumerates the combinations and their expected outcomes, surfacing a rule nobody specified: high income but high debt. Testing that overlooked combination reveals the system wrongly approves it.
How should you talk about Decision Table Testing in an interview?
Explain the structure (conditions as rows, each column a combination/rule, actions at the bottom) and say it is for logic driven by multiple interacting conditions. Mention collapsing impossible combinations and pairing it with equivalence partitioning.
Go Deeper on Decision Table Testing
Know the term. These are the courses that turn the concept into something you can demonstrate.
Common questions about Decision Table Testing
When should you use decision table testing?
Use it when behavior depends on combinations of multiple conditions, business rules like pricing, eligibility, discounts, or permissions. The table forces you to consider every meaningful combination instead of guessing.
How many test cases does a decision table produce?
With N independent boolean conditions there are up to 2^N combinations (columns). In practice you collapse impossible or equivalent combinations to keep the number of test cases manageable while preserving coverage.
Which terms relate to Decision Table Testing?
Explore related glossary terms to deepen your understanding.
Related Resources
Dive deeper with these related interview prep pages.
Free QA career tools, no account needed
Instant and private, everything runs in your browser. Try them before you sign up.
QA Resume Checker
Instant 0-100 score on automation keywords, impact, and ATS formatting.
QA Cover Letter Generator
A tailored 3-paragraph QA cover letter from your resume and a job post.
QA Application Tracker
Drag-and-drop kanban to track every QA application from Applied to Offer.
QA Take-Home Test Generator
A realistic take-home assignment with a scenario, tasks, and a rubric.
QA LinkedIn Headline Generator
A recruiter-searchable headline, About section, and skills list.
QA STAR Story Builder
Structure a QA behavioral answer with the STAR method and instant checks.
QA Bug Report Generator
Build a clean, reproducible bug report for Markdown, Jira, or plain text.
Boundary Value Analysis Generator
Generate boundary value and equivalence partitioning test cases from a range.
QA Metrics Calculator
Calculate DRE, defect leakage, defect density, and pass rate with interpretation.
QA Test Plan Generator
Build a structured test plan (scope, approach, criteria, risks) in Markdown.
QA Salary Calculator
Estimate QA, SDET, and automation tester pay by level, market, and skills.
QA Offer Evaluator
See total comp, a counter range, and a ready-to-send negotiation message.
Ready to Ace Your QA Interview?
Practice explaining decision table testing and other key concepts with our AI interviewer.
Join 500+ QA engineers already practicing with AssertHired.
A test passes locally but fails in CI about one run in five. Walk me through what you check first, and why.
Scored on the same four dimensions as the real thing: Technical accuracy · Coverage · Clarity · Best practices.
Rather skip ahead? Create a free account