If you’re using Travis CI, Code Climate, or one of many other CI tools with Github, you’ve probably noticed the little checklist of items that shows just above the “merge” button when you open a pull request.
How we create Consumer Driven Contract tests to make sure our applications are working well with each other when using two frontend applications both of which are consuming common microservice APIs.
Imagine - you’re on a team writing an app that uses three different HTTP APIs, and you’ve decided to use consumer contracts to test your integrations.
With the move to microservices, or µ-services for the more stylish, Consumer Driven Contract testing with Pact evolved as a strategy to be able to determine if all of our services will talk correctly to each other. Without requiring all of our services to talk to each other. It also allowed us to identify who the consumers of any service were. This was helpful, because if you know who your consumers are, you know who to talk to when you want to break something. Or when they break something.
