Convergence Metric
A convergence metric measures progress toward completing testing or achieving predefined testing objectives over time.
“A metric that shows progress toward a defined criterion, e.g., convergence of the total number of tests executed to the total number of tests planned for execution.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Convergence Metric?
Convergence metrics help determine whether testing activities are approaching completion by tracking trends such as defect discovery, execution progress, or remaining risks.
Progress measurement: Indicates how testing advances toward completion.
Trend analysis: Helps predict when testing goals will be achieved.
Decision support: Assists release and project planning.
Real World Example
A regulated product team is preparing a release where Convergence metric appears in reviews, test design conversations, or defect triage rather than as an isolated glossary word.
The risk is that the team treats Convergence metric 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 Convergence metric and similar ideas.
The page becomes useful in practice because Convergence metric is connected to a specific testing decision, not memorized as a detached definition.
Practice Questions
Question 1
Which statement BEST describes Convergence metric in the context of ISTQB terminology?
Question 2
A tester needs to explain Convergence metric to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned Convergence Metric. Test your understanding with topic-specific questions in our Mock Exams.