Pact Contract Testing for Quarkus

[@rahulkohli3043]

Can you share the link to the repo

[@kanaillaurent526]

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.

[@marcschlegel713]

@PactTestFor and @Pact are Annotations from Pact-JVM, not Quarkus. I havent seen Pact in other languages but Pact-Jvm is in my opinion not very good. For instance in PactTestFor you have to name a method which is then looked up via reflection in order to create the Pact-Contract (which it then tests against). The api is horrible as well: there is for instance an option to pass examples as varargs array to a field definition, but during runtime Pact tells you that you can only pass one example value...why is it a varags array then? By the way, I am using Pact for 2 years now and I can understand why architects like the idea (considering hello world examples) but the technical solution has so many open issues and even if they would be solved you cannot get full confidence in your integration because a tool can never solve human mistakes

[@rahulkohli3043]

Can you share the repo link?