Eight Chapter 4 questions from the supplied ya01a quiz, rebuilt as guided worked examples. Read the question, try it yourself, then reveal the step-by-step reasoning and visual solution.
Chapter 48 QuestionsGuided Solutions
Q4
4
How to use this workshop
The revision notes map Chapter 4 to Q2, Q3, Q4, Q18, Q20, Q22, Q28 and Q29. Work each question before revealing the solution. The solution table separates the reasoning into small decisions so you can reuse the method on similar exam questions.
1. Identify
Spot the syllabus topic and the key words in the question.
2. Apply
Use the technique or definition, not intuition alone.
3. Eliminate
Check why each distractor is weaker or invalid.
4. Conclude
Select the answer only after the evidence is clear.
★
Chapter 4 Exam Patterns
EP
Count distinct partitions covered, not the number of test values.
BVA
Compare expected and faulty behavior at the boundary and its neighbors.
State transitions
Reject invalid transitions first, then count distinct valid transitions.
Definitions
Match the wording precisely: specification → black-box; structure → white-box; experience → experience-based.
Chapter 4 interactive study guide covering test-technique selection, black-box, white-box and experience-based techniques, plus collaboration-based test approaches.
Chapter 4CTFL v4Interactive Study Map
TAD
04
Test Analysis and Design
Test techniques provide systematic ways to derive test conditions, test cases and test data. Chapter 4 groups the core techniques by the source of knowledge used about the test object.
Chapter map
4.1 Overview → choose and distinguish techniques. 4.2 Black-box → EP, BVA, decision tables, state transitions. 4.3 White-box → statement and branch testing. 4.4 Experience-based → error guessing, exploratory, checklist-based. 4.5 Collaboration-based → user stories, acceptance criteria and ATDD.
4.1
Test Techniques Overview
The Foundation Level material distinguishes three main categories according to the source used to derive tests.
Category
Primary source
Typical focus
Black-box
Requirements, specifications, use cases, user stories
Discrepancies between specified and implemented behavior
White-box
Internal structure such as code, architecture or detailed design
Control-flow and structural problems
Experience-based
Knowledge, experience and intuition of stakeholders
Problems suggested by experience, risks and known failure modes
Nine core techniques
Four black-box + two white-box + three experience-based techniques form the main Foundation Level technique set.
4.2
Black-Box Test Techniques
Black-box techniques derive tests from externally visible behavior and specifications without depending on the internal implementation.
4.2.1
Equivalence Partitioning
Divide a domain into equivalence partitions whose members are expected to be processed in the same way, then test representative values.
Valid partitions
Contain values accepted by the specification. One representative can exercise a partition.
Invalid partitions
Contain values that violate the specification. Invalid partitions should also be considered where applicable.
Coverage
Number of partitions exercised by at least one test value divided by the total identified partitions.
Exam cue
In multidimensional problems, combining several invalid conditions in one test may cause defect masking. Treat the selected domain and partition model carefully.
4.2.2
Boundary Value Analysis
BVA extends equivalence partitioning by concentrating tests on the edges of ordered partitions, where implementation errors are common.
Example boundary: x ≤ 10
9→10 boundary|11 boundary→12
2-value BVA focuses on boundary values; 3-value BVA also includes neighboring values and can detect some defects that 2-value BVA misses.
Applicability
BVA requires an ordered domain and contiguous partitions so that smallest/largest elements and their neighbors are meaningful.
4.2.3
Decision Table Testing
Decision tables systematically test business rules involving combinations of conditions and resulting actions.
Rule
C1
C2
Action
R1
T
T
A
R2
T
F
B
R3
F
T
C
R4
F
F
D
Method
Identify conditions → identify actions → generate feasible condition combinations → determine actions for each rule → derive test cases from the rules.
4.2.4
State Transition Testing
Use a state model when system behavior depends on its current state and an event can cause a transition, action or invalid transition.
State Aevent →State Bevent →State C
State coverage
Exercise identified states.
Valid-transition coverage
Exercise valid transitions represented by the model.
Invalid transitions
Check events that should not cause a valid transition from a given state.
4.3
White-Box Test Techniques
White-box testing derives coverage items from the internal structure of the test object, commonly represented by code or a control-flow graph.
4.3.1
Statement Testing and Coverage
Statement testing designs tests to execute executable statements.
Choose any of the nine CTFL test techniques. Each guide gives you an exam-style example, lets you think through the problem, and then reveals a suggested solution with the reasoning and coverage calculation where applicable.