CTFL-v4 Test Analysis and Design Practice Question
A tester is designing test cases for a library management system. The system calculates fines for overdue books based on the number of days late and the borrower type (student or faculty). For students, the fine is $0.25 per day; for faculty, it is $0.50 per day. The system also waives fines if the book is returned within 3 days. Which test design technique would be most effective to systematically cover combinations of borrower type, days late, and waiver condition?
⚠ Common exam trap
The trap here is assuming that boundary value analysis or equivalence partitioning alone can handle multi-condition business rules, when they focus on individual inputs rather than combinations.
Answer choices
Why each option matters
Answer the question above first, then reveal the full breakdown to understand why each option is right or wrong.
Correct answer & explanation
✓
Decision table testing
Decision table testing is the best fit because the fine calculation depends on a combination of conditions: borrower type, days late, and whether the waiver applies. A decision table systematically lists all combinations of these conditions and the corresponding actions, ensuring comprehensive coverage of the business rules. This technique is specifically designed for complex logical rules and helps identify gaps or contradictions in requirements.
Answer analysis
Option-by-option breakdown
For each option: why learners choose it and why it is or isn't the right answer here.
- ✗
Boundary value analysis
Why it's wrong here
Boundary value analysis focuses on testing values at the edges of input ranges, such as days late being 0, 3, 4, etc. While useful for numeric inputs, it does not systematically cover the combination of borrower type and waiver condition with days late. It would test boundaries but not the full rule set, potentially missing interactions between borrower type and waiver.
- ✗
State transition testing
Why it's wrong here
State transition testing models systems that have distinct states and transitions triggered by events. In this scenario, the fine calculation does not involve a sequence of states; it depends on combinations of conditions at a single point. Using state transition testing would not address the combinatorial nature of borrower type, days late, and waiver, and would likely miss rule combinations.
- ✗
Equivalence partitioning
Why it's wrong here
Equivalence partitioning divides inputs into classes where behavior is expected to be the same, reducing test cases. However, it does not explicitly handle combinations of multiple conditions. In this scenario, borrower type and waiver condition create distinct partitions, but the interaction with days late requires more than partitioning to ensure all business rules are validated.
- ✓
Decision table testing
Why this is correct
Decision table testing is ideal for business rules with multiple input conditions and corresponding actions. Here, conditions like borrower type, days late, and waiver eligibility determine the fine. A decision table ensures all combinations of these conditions are covered, including cases where the waiver applies or not, and different borrower types. This systematically verifies the fine calculation logic and catches inconsistencies.
About these practice questions
One of 144 original CTFL-v4 practice questions on Courseiva, each with a full explanation and wrong-answer analysis — not exam dumps or protected exam content. Learn why practice questions differ from exam dumps →
JA
Written and reviewed by Johnson Ajibi, MSc IT Security
Senior Network & Security Engineer · founder of Courseiva
Last reviewed September 2026 · checked against the official ISTQB exam blueprint
This CTFL-v4 practice question is part of Courseiva's free ISTQB certification practice question bank. Courseiva provides original exam-style practice questions with explanations, topic-based practice, mock exams, readiness tracking, and study analytics to help learners prepare for the CTFL-v4 exam.