Contract Testing
Consumer-Driven Contract Testing: What It Is and Why It Matters
Consumer-driven contract testing flips the typical API design relationship.
Microservices
Latest
Testing
Pact vs Integration Tests: When to Use Contract Testing
"Should we use Pact or integration tests?" is a question that comes up whenever a team starts decomposing a monolith into services.
Testing
PactFlow: Managing Contracts at Scale in a Microservices Architecture
Local pact files work fine when you have one consumer and one provider. As soon as you have five consumers and ten providers, file-sharing falls apart.
Testing
Pact with Node.js and Express: API Contract Testing Step by Step
Contract testing with Pact shines brightest in Node.js microservice environments.
Testing
Contract Testing in CI/CD: Pact with GitHub Actions and Jenkins
Contract tests are only valuable if they run automatically and block bad deployments. A pact that exists locally but isn't in your CI pipeline is theater.
Testing
Pact Testing Tutorial: Consumer-Driven Contract Testing in 30 Minutes
Microservices break in integration. A provider team updates an API response format, the consumer team doesn't know for two weeks, and then production falls over. The standard answer — integration tests against a shared staging environment — is slow, flaky, and doesn't scale. Pact takes a different approach: