Statement Testing
Statement testing is a white-box test technique that designs test cases to execute every executable statement in the program at least once.
“A white-box test technique in which test cases are designed to execute statements.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Statement Testing?
The technique aims to satisfy statement coverage by ensuring all code statements are exercised during testing.
Execution focus: Every statement should run at least once.
Coverage objective: Achieves statement coverage.
Foundation technique: One of the simplest structural testing methods.
Visual Example
Simplified state transitions
Arrows omitted for clarity
Real World Example
A mobile banking app lets customers freeze, unfreeze, replace, and cancel debit cards from the app.
The same button can be valid in one card status and invalid in another. Statement testing matters because the defect risk sits in movement between statuses, not just on individual screens.
The tester follows each allowed and blocked transition, such as frozen to active or cancelled to reissued, and checks that the app prevents impossible card states.
Understanding Statement testing helps the team protect customers from cards being left active, unusable, or shown with the wrong status after an action.
Practice Questions
Question 1
A team's full regression suite passes, but a coverage tool reports 82% statement coverage on the module under test. What does this MOST directly tell the tester?
Question 2
A shipping cost function applies an international surcharge only inside a rarely used branch, and a coverage report shows that line has never executed. Which test addition is the MOST direct fix for statement testing purposes?
Test your knowledge with real ISTQB-style questions
You’ve learned Statement Testing. Test your understanding with topic-specific questions in our Mock Exams.