Challenges of microservices contract testing: quick, low-code and at scale with Microcks
Tools-in-Action (BEGINNER level)
Dhalia
You’ve just deployed this brand new cool < REST | GraphQL | gRPC > microservice that perfectly suits the business requirements. Or at least, that’s your gut feeling… You’d like to keep the pace high, avoiding the expense and pain of end-to-end testing to check that. Enter the world of contract testing!
Your challenge: set up something to guarantee both technical and functional conformance quickly. You need something easy, low-code in order to scale with your org whilst still giving you a very high level of confidence. Enter Microcks, an open-source cloud-native tool (CNCF Sandbox project), ready to work with Testcontainers, that provides a solution for mocking and testing APIs without extensive coding.
In this session, we will go through "tools in action"' mode to illustrate how Microcks can be used to ensure different kinds of conformance, leveraging existing artifacts like OpenAPI, Postman Collection, or others. We’ll finally see how to automate this to establish a robust delivery chain.
Your challenge: set up something to guarantee both technical and functional conformance quickly. You need something easy, low-code in order to scale with your org whilst still giving you a very high level of confidence. Enter Microcks, an open-source cloud-native tool (CNCF Sandbox project), ready to work with Testcontainers, that provides a solution for mocking and testing APIs without extensive coding.
In this session, we will go through "tools in action"' mode to illustrate how Microcks can be used to ensure different kinds of conformance, leveraging existing artifacts like OpenAPI, Postman Collection, or others. We’ll finally see how to automate this to establish a robust delivery chain.
Laurent Broudoux
Microcks
Laurent is a Cloud-Native Architecture expert and Enterprise Integration problem lover. He is the founder and lead developer of the Microcks.io open source project: a Kubernetes-native tool for API mocking and testing. For this, he is using his 10+ years experience as an architect in Financial Services where he defined API transformation strategies, including governance and delivery process.