Compliance Testing
Compliance testing verifies that software, processes, or systems satisfy applicable standards, regulations, contracts, or organizational policies.
“Testing to determine the compliance of the component or system.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Compliance Testing?
Compliance testing provides evidence that a product meets mandatory requirements before deployment, certification, or regulatory approval.
Requirement verification: Tests confirm that mandatory obligations are satisfied.
Documentation: Test results often support audits and certification activities.
Industry usage: Common in finance, healthcare, automotive, and government projects.
Real World Example
A regulated product team is preparing a release where Compliance testing appears in reviews, test design conversations, or defect triage rather than as an isolated glossary word.
The risk is that the team treats Compliance 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 Compliance testing and similar ideas.
The page becomes useful in practice because Compliance testing is connected to a specific testing decision, not memorized as a detached definition.
Practice Questions
Question 1
Which artifact MOST supports compliance testing claims?
Question 2
Which is the MAIN objective of compliance testing?
Test your knowledge with real ISTQB-style questions
You’ve learned Compliance Testing. Test your understanding with topic-specific questions in our Mock Exams.