What is API Contract Testing?
Turkish: API Sözleşme Testi
API contract testing compares consumer expectations with provider responses through contracts such as OpenAPI or Pact.
What is API Contract Testing?
API contract testing verifies that the expectations between an API provider and its consumers remain compatible. A contract defines endpoints, methods, required fields, data types, error codes, and example responses.
In a microservice architecture, one team can remove a customerId field and silently break another team’s service. Contract testing is designed to catch that kind of change before it reaches production. With tools such as Pact, the consumer defines the interaction it expects, and the provider proves that the real API satisfies it.
How It Is Applied
- An OpenAPI schema or Pact contract is stored in version control.
- Consumer tests generate the expected requests and responses.
- Provider tests check that the actual API follows the contract.
- The CI/CD pipeline blocks incompatible changes before release.
Business Use
If API testing depends only on end-to-end scenarios, defects are found late and tests become brittle. Contract testing gives earlier feedback, especially in multi-team microservice environments.
For public APIs, contract testing also supports versioning policy. Breaking changes should be handled with documentation, changelogs, and customer communication, not only a code release.
Related Terms
API testing validates endpoint responses, error codes, performance, and authorization behavior through repeatable test scenarios.
CI/CD (Continuous Integration / Continuous Delivery)CI/CD makes software releases repeatable by moving code changes through automated build, test, and deployment pipelines.
MicroserviceMicroservice architecture designs a large application as small services that can be developed, deployed, and scaled independently.