Quality Debt
Quality debt is the accumulated impact of postponing quality-related work, resulting in increased future effort, cost, or risk.
“The implied cost of deferred quality assurance activities.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Quality Debt?
Examples include deferred testing, poor documentation, weak automation, or unresolved defects that reduce long-term product quality.
Long-term impact: Delayed quality work becomes more expensive later.
Different from technical debt: Focuses specifically on quality activities.
Risk accumulation: Unresolved quality issues increase future project risk.
Real World Example
A regulated product team is preparing a release where Quality debt appears in reviews, test design conversations, or defect triage rather than as an isolated glossary word.
The risk is that the team treats Quality debt as interchangeable with nearby ISTQB terms. That makes test scope blurry and can lead to weak evidence for the release decision.
The tester anchors the discussion in the official definition, asks where the concept appears in the product, and designs examples that show the difference between Quality debt and similar ideas.
The page becomes useful in practice because Quality debt is connected to a specific testing decision, not memorized as a detached definition.
Practice Questions
Question 1
Which statement BEST describes Quality debt in the context of ISTQB terminology?
Question 2
A tester needs to explain Quality debt to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned Quality Debt. Test your understanding with topic-specific questions in our Mock Exams.