Hi all, and thanks for helping in advance. In the company that I working for, contract tests were added, it understood why we need it and the value. We have a use case that was talked in our company and we would like to hear the opinion here from the pact’s experts, to understand what better to do. Use case: A msg contract was added. There is a service, that is kind of monolit, the service also send msg (by queue) and the same service consume this queue (maybe other instance). Question: Should we create a contract test for this use case? From one side: it more sensible that contract should be between 2 services. From the other side: this is a big service and we still want to verify that nothing break. Would like to hear your opinon. @Arnon Ram FYI

It might be worth asking a few other questions: 1. What other protections do you have in place for this if you didn’t use Pact? 2. What’s the harm in trying it? One issue you will probably run into is deadlocks in builds where a consumer is waiting for a provider (itself) or vice versa.

thanks for your comment. 1 - tests inside the serivce 2 - it will work, but from design aspect, if it is true. Regarding the ppossible issuee, it is know, should sepeprate the level of the consumer and provider test (will not be in parallel)