False-negative Result
A false-negative result occurs when a test incorrectly indicates that a defect, vulnerability, or condition is absent when it actually exists.
“A test result which fails to identify a defect that is actually present in a test object.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is False-negative Result?
False negatives reduce confidence in testing because real problems remain undetected and may reach production.
Missed detection: Existing issues are reported as not present.
Testing risk: Undetected defects can affect users after release.
Quality impact: High false-negative rates reduce testing effectiveness.
Real World Example
A regulated product team is preparing a release where False-negative result appears in reviews, test design conversations, or defect triage rather than as an isolated glossary word.
The risk is that the team treats False-negative result 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 False-negative result and similar ideas.
The page becomes useful in practice because False-negative result is connected to a specific testing decision, not memorized as a detached definition.
Practice Questions
Question 1
Which statement BEST describes False-negative result in the context of ISTQB terminology?
Question 2
A tester needs to explain False-negative result to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned False-negative Result. Test your understanding with topic-specific questions in our Mock Exams.