Defect Workflow
A defect workflow defines the sequence of states and activities that a defect follows from discovery to closure.
“The state transition model of a defect lifecycle, including responsibilities.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Defect Workflow?
The workflow establishes how defects are reported, assigned, resolved, verified, and closed, ensuring consistent defect management across the project.
Lifecycle states: Common states include New, Assigned, Fixed, Verified, Reopened, and Closed.
Responsibilities: Each workflow stage identifies who is responsible for the next action.
Traceability: Workflow history provides visibility into defect progress.
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. Defect workflow 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 Defect workflow helps the team protect customers from cards being left active, unusable, or shown with the wrong status after an action.
Practice Questions
Question 1
Which statement BEST describes Defect workflow in the context of ISTQB terminology?
Question 2
A tester needs to explain Defect workflow to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned Defect Workflow. Test your understanding with topic-specific questions in our Mock Exams.