Hopefully, you can now start to see how changing the perspective of test by embracing the consumer perspectives can be a powerful testing technique, especially for Microservices.
With an established library of contacts, a producer writer can have much more confidence when making adjustments to the API that others consumer. With any change they can run pactVerify, to help understand the impact of changes to their consumers.
Consumers can work with customer requirements and evolving APIs by mocking up new communication scenarios. Those new contacts can be published and verified against their providers. The Pacts provide opportunities for conversations and understanding impacts of change while maintaining a clean separation between the producers and consumers.
With these steps you have learned how to:
- ✔ set up a Pact Broker on Kubernetes
- ✔ write a consumer that defines and publishes Pact contracts
- ✔ deploy and run a few Spring Boot microservices on Kubernetes
- ✔ connect microservices to a database and public data source
- ✔ verify the consumer pacts against a producer
- ✔ find API defects and fix them
For a deeper understanding of these topics and more join
at various conferences, symposiums, workshops, and meetups.
Software Architectures ★ Speaker ★ Workshop Hosting ★ Kubernetes & Java Specialist