Negative Testing
Negative testing verifies that software behaves correctly when given invalid, unexpected, or erroneous inputs and conditions.
“A test type in which a component or system is used in a way that it is not intended.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Negative Testing?
The objective is to confirm that the system handles errors gracefully without crashing, exposing security issues, or producing incorrect results.
Invalid input: Tests unexpected or prohibited values.
Error handling: Verifies meaningful messages and stable behavior.
Robustness: Ensures the application resists misuse and incorrect usage.
Real World Example
A regulated product team is preparing a release where Negative testing appears in reviews, test design conversations, or defect triage rather than as an isolated glossary word.
The risk is that the team treats Negative testing 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 Negative testing and similar ideas.
The page becomes useful in practice because Negative testing is connected to a specific testing decision, not memorized as a detached definition.
Practice Questions
Question 1
Which statement BEST describes Negative testing in the context of ISTQB terminology?
Question 2
A tester needs to explain Negative testing to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned Negative Testing. Test your understanding with topic-specific questions in our Mock Exams.