Pact Contract Testing for Quarkus

Every time you change one microservice, others break. But you had unit tests! What’s going on? Unfortunately, unit tests aren’t enough to give system-level confidence, even with a microservices architecture.

What’s the solution? Integration testing is annoying, expensive, flaky, and fries your laptop.
Remocal development environments are complex to manage. Testing in production is important, but the feedback loop is longer, so it’s not a substitute for local inner-loop testing.

This is where contract tests come into play. Contract tests combine the lightness of unit tests with the confidence of integration tests, and they should be part of your development toolkit. This session will demo how to use the Pact contract testing framework to catch integration issues early. The demos will be run on Quarkus, but Pact runs on all Java frameworks. Pact has libraries for almost all of the popular programming languages.

Speaker: Holly Cummins

Join us:


#contracttesting #microservicetesting #java

[kanaillaurent]

I didn't had good experience at all with Spring because all of the magic behind the annotations and there are sooo many annotations and many if them can do actually the same and it's a mess and it's always changing. I really hope quarkus is not going in the same direction. But when I see the exemples in the video I'm afraid it's actually the same problem. @quarkustest, @Pacttestfor @pact.... What does it do? Will I have again to read whole bunch of document? Feels like another trap to me.