-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial support for bi-directional contracts (OAS/Swagger) #4
Comments
Potential "evidence" to support:
|
We're going to defer this until after feedback from our developer preview group. |
Note to self: Current oas verifiers say "We've seen no evidence that this spec is wrong" rather than "the code fully implements what is described in the spec" |
Any update on this? |
It's currently in developer preview, and you can use it now. You can see the docs for this: https://docs.pactflow.io/docs/workshops/bi-directional/ We're progressively rolling the UI support out for this over the next little while, so this has been kept as open whilst we are still in preview. |
Enable support for a bi-directional contract testing workflow with Open API Spec as the initial provider contract.
The initial workflow will support:
can-i-deploy
phase)TODO
Deferred
* [ ] provide an endpoint to allow pact/OAS verification to be done before publishing a pactFollow up:
See also https://pactflow.io/blog/the-curious-case-for-the-provider-driven-contract/ and pact-foundation/pact-specification#76 for some background.
The text was updated successfully, but these errors were encountered: