Home > Glossary > Certified Tester Foundation Level > Condition (Decision Table)

📖 What is Condition (Decision Table)?

A Condition in a decision table represents an input or a specific state of the software that affects its behavior. Conditions are typically listed in the top half of the table and evaluated as True or False.

🥋 Sensei Says:

"Pay close attention to how conditions interact. If a condition's outcome doesn't change the action, it might be an 'immaterial' or 'don't care' condition, allowing you to reduce your test cases."

📚 Certification: Certified Tester Foundation Level (CTFL-v4.0)

🔑 What are the Key Concepts of Condition (Decision Table)?

▸ Input or state affecting behavior
▸ Evaluated as True or False
▸ Listed in the top half of the table
▸ Can be material or immaterial

🎯 How does Condition (Decision Table) appear on the CTFL-v4.0 Exam?

Identify immaterial conditions in a rule.

Determine how many conditions exist in a given specification.

Map system inputs to decision table conditions.

❓ Frequently Asked Questions

What is an immaterial condition?

A condition whose outcome doesn't affect the action for a rule.

Are conditions always boolean?

Typically yes, though extended entry tables allow multiple discrete values.

Related Terms from Certified Tester Foundation Level

Formal Review Project Risk Test Execution Tool Action (Decision Table) Testing Inspection

📝 Related Study Guides

Study Guide 10 min read

How to Pass ISTQB CTFL v4.0 on Your First Try

To pass the ISTQB CTFL v4.0 on your first try, focus heavily on Chapter 4 (Test Analysis and Design), which accounts for 27.5% of the exam. Combine the official syllabus with high-volume practice exams, aiming for a consistent 80% score. Dedicate 4-6 weeks of study, prioritizing active recall over passive reading.

Deep Dive 10 min read

Equivalence Partitioning vs Boundary Value Analysis: ISTQB

Equivalence Partitioning (EP) divides input data into groups that should be processed identically, reducing test cases by testing one representative value per group. Boundary Value Analysis (BVA) complements this by testing the edges of these partitions, where defects frequently occur, ensuring the system handles limits and transitions correctly.

Study Guide 8 min read

What is Software Testing? ISTQB CTFL v4.0 Chapter 1 Deep Dive

Software testing is a comprehensive process that involves both static and dynamic activities designed to evaluate software quality. It aims to find defects, verify requirements, build confidence in the system, and provide critical information to stakeholders for decision-making.