Hi Community, I have a question about BDCT. On Consumer side we have an iOS app implementing traditional PACT. On our provider side, we have OAS available and we think that we could generate the PACT file by implement BCDT using RestAssured. Is this compatible? In the documentation we saw: Compatible with Consumers This project is currently compatible with the following consumers(s): • pactflow-example-bi-directional-consumer-nock • pactflow-example-bi-directional-consumer-msw • pactflow-example-bi-directional-consumer-wiremock • pactflow-example-bi-directional-consumer-mountebank Does it mean Bidirectional feature is not compatible with PACT contracts?

Hey hey, Each of those consumers, use consumer testing tools native mock capabilities, and then converts successful matches to Pact specification format files. If you already have a consumer generating consumer pact files via a Pact client library framework, this is the ideal scenario. You can indeed use BDCT to compare that consumer pact file with the OAS of your provider. Are you currently doing provider verification with a Pact client library, for for provider? BDCT will not utilise provider states, or matchers so that is one caveat to be aware of, but these won't stop you from doing the pact -> oas comparison