Testing
Contract Testing Between Micro-Frontends
Micro-frontends communicate through defined interfaces: federated module exports, custom events, shared state, and props passed from shell to remote.
Testing
Micro-frontends communicate through defined interfaces: federated module exports, custom events, shared state, and props passed from shell to remote.
Testing
Your application integrates with Stripe, GitHub, Twilio, SendGrid, and Slack. Each needs tests. But which kind?
Contract Testing
Specmatic turns your OpenAPI specifications into executable contracts that work from both sides: it can run your spec as a stub server for consumer testing, and verify that your actual API implementation conforms to the spec for provider testing. One spec file, both directions — without writing a single test. The
API Testing
Dredd validates that your API implementation matches its documentation.
Contract Testing
Spring Cloud Contract is the contract testing framework for Java Spring applications.
Contract Testing
Contract testing and integration testing both verify that services work together correctly.
Contract Testing
Microservice architectures break monoliths into independently deployable services.
Contract Testing
This tutorial walks through implementing Pact contract testing in a Node.js microservice architecture.
Contract Testing
Consumer-driven contract testing flips the typical API design relationship.
Testing
"Should we use Pact or integration tests?" is a question that comes up whenever a team starts decomposing a monolith into services.
Testing
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
Contract testing with Pact shines brightest in Node.js microservice environments.