Contract Testing
Contract testing verifies that two interacting systems comply with the agreed interface contract without requiring full end-to-end testing.
“A type of integration testing that verifies that the interfaces are used as specified in their contracts.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Contract Testing?
Contract testing ensures that service providers and consumers exchange requests and responses exactly as defined by an API or service contract.
Service contracts: Define expected requests, responses, formats, and behaviors.
Provider and consumer: Both sides independently verify compliance with the contract.
Benefits: Detects integration issues early while reducing dependence on shared environments.
Real World Example
An insurance claims platform is connecting a claim intake service, a policy validation service, and a payment approval service.
Each part can look correct in isolation while the handoff between parts still fails. Contract testing helps testers focus on the boundary where data, timing, and responsibility meet.
The tester checks payloads, error handling, retries, missing fields, and the order of service calls instead of only confirming that each screen appears.
The claims flow becomes more dependable because Contract testing exposes defects that only appear when real components collaborate.
Practice Questions
Question 1
Which statement BEST describes Contract testing in the context of ISTQB terminology?
Question 2
A tester needs to explain Contract testing to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned Contract Testing. Test your understanding with topic-specific questions in our Mock Exams.