Pact Foundation

Hi Bernard! We don’t have a way to generate a pact file from an OAS (that would be a <https://docs.pact.io/faq/#can-i-generate-my-pact-file-from-something-like-swagger|bad idea>)

Hi <@U9UUY3CU9> referring to the *bad idea* link I actually meant to "_generate skeleton Pact test code from a Swagger document_".

I guess it could be done, but then we’d need to do that for each language, and then for each test framework. I’m not convinced of its utility, personally.

Also, you then would need to remove any parts of the OAS you’re not using, so I think it’s likely to lead to consumers inadvertently requesting more of what they need of a provider

But I’m open to a PR or something that could do it - I don’t think it would be terribly difficult. We’re always very conscious of creating more tools, because that means:

1. More code to support and bugs to fix, across (currently) 10+ languages
2. More documentation/tutorials/workshops etc. needs to be written, managed and updated
3. More components to consider when adding new major features to Pact
So it’s something we’d want to be really sure about!

What are you using at the moment to mock the provider APIs in your consumer code bases? There is potentially _another_ way

Hi <@U9UUY3CU9> we're at POC stage right now. I spoke to your colleague earlier this morning (GMT) and I think all the above can be avoided if I look into <https://docs.pactflow.io/docs/workshops/bi-directional|bi-directional contracts>. Is that right from my understanding?

I'm currently using the Pact consumer/provider GitHub example. I've completed the CI/CD workshop. And I've added Cypress.

I've applied to your developer program and I'm waiting on a response to my application.

To my understanding, if I'm accepted... There will be information about creating a provider contract using OAS which I can employ to further our POC.

Which page on the docs site, referred you?

I was looking for information about bi-directional contracts and ended up on the <https://docs.pact.io/help/how_to_ask_for_help/|How to ask for help on Slack> after a Google search.

In any case, Pactflow has a new feature (in dev preview) called <https://docs.pactflow.io/docs/workshops/bi-directional|bi-directional contracts>. It allows you to use the OAS as a provider contract, but the consumer still needs to publish a consumer contract. This can be via a standard Pact test, or by converting existing mocks into a pact file. This way, you still know what the consumer needs, and Pactflow can ensure the provider meets those needs.

Hi <@U9UUY3CU9> I have a question, so basically we create the pact at the consumer side publish it to the pact broker, and the provider just verifies that contract right? (ofcourse we create the provider states) but only one contract is created which is verified by the provider.

And in bi-directional flows we create contracts at both sides?

Yes, the first is describing standard consumer driven contract testing

bi-directional is more decoupled, each side produces their own contract and we just ensure they are compatible