Hi, i just had a meeting where i was trying to explain that contract testing should only test the contract; ideally stub out (aka mock) the downstream software components and services as thats the concern of other tests. Of course there may be exceptions to this ideal (very small service/laziness/some other reason). The issue I was advising against, was trying to drive your apps berhavioural testing et al (say in the provider - starting at the top layer) as giant 'integration' tests through pact - thats not the responsibility of PACT and you can get very complicated flakey pacts and harder to maintain code (i.e. you can get yourself into trouble). I do recall a video by @Beth (pactflow.io/Pact Broker/pact-ruby) on youtube, that i believe covered this subject, not sure if anyone can link me it (i cant find the right one) ? or comment; am I wrong - is my advice poor ? Thanks!! 😉

That's correct! Here's some related links • https://pactflow.io/blog/a-disastrous-tale-of-ui-testing-with-pact • https://docs.pact.io/consumer#watch-a-video-writing-good-consumer-tests

excellent thanks!! 🙂