Search the practice set
126 questions, 454 terms and 400 topics in 20 areas.
16 results for “Contract Tests”
Contract Testing
Verifying that a provider satisfies the expectations each of its consumers actually relies on, without running all the services together.
Data Contract
An explicit, versioned, enforced agreement between a data producer and its consumers about schema, semantics, quality and change policy.
Abstraction
Exposing what a component does while hiding how it does it, so callers depend on the contract rather than the mechanism.
Circuit Breaker
A proxy that stops calling a failing dependency after a failure threshold, failing fast instead, and periodically tests whether it has recovered.
Semantic Diffing of API Schemas
Comparing the published contract between builds and failing the build on a breaking change, so compatibility is mechanical rather than remembered.
Test Pyramid
A distribution of tests weighted towards many fast unit tests, fewer integration tests, and very few slow end-to-end tests.
Zero-Downtime Migration
Changing a schema or system while it stays in service, by adding the new alongside the old, migrating, then removing the old.
gRPC
A contract-first RPC framework using Protocol Buffers over HTTP/2, with generated clients and servers and first-class streaming.
Contract Tests
Capturing what consumers actually use, not what the API documents.
Testing Strategies
The pyramid, and the contract tests distributed systems add to it.
Contract Testing
Verifying what consumers actually rely on, without a shared environment.
API Documentation
OpenAPI as a machine-checked contract rather than as prose.
Abstraction & Encapsulation
Hiding mechanism behind contract, and protecting invariants by owning state.
Capacity Modelling
Arithmetic before load tests, and headroom for failure as well as peak.
Zero-Downtime Migration
Expand, migrate, contract — and the contract phase that never happens.
gRPC APIs
Contract-first RPC, generated clients and protobuf compatibility rules.