Hi all, when utilizing bidirectional contract test...
# pactflown
Noor Hashem
08/31/2022, 4:48 PMHi all, when utilizing bidirectional contract testing do we need to verify the provider contract? For example if we have openapi documentation that is well kept, do we need the additional step of using postman for verification? Wouldn't postman redundantly recreate the openapi spec for us?? I see in the video here: we use postman to actually generate the openapi spec. But for our team we have openapi spec already.
m
Matt (pactflow.io / pact-js / pact-go)
08/31/2022, 10:06 PM
It's not about recreating the spec, it's about ensuring your provider is compliant with the spec. However you do that we don't mind
Matt (pactflow.io / pact-js / pact-go)
08/31/2022, 10:07 PM
In that example we use a postman collection (the tests) and convert to a spec, so we know whatever is generated is valid)
Matt (pactflow.io / pact-js / pact-go)
08/31/2022, 10:08 PM
If you already have a spec then how do you ensure your API is correct?
Matt (pactflow.io / pact-js / pact-go)
08/31/2022, 10:09 PM
For what it's worth I don't think postman is a good tool for this, but Portman might be ok
n
Noor Hashem
09/01/2022, 1:33 PMOkay I see what you mean. Now that I have a yaml openapi file that is checked how can I publish it to pactflow directly? I see many different ways to do it but i'm looking for just a simple way to directly publish a yaml openapi file
m
Matt (pactflow.io / pact-js / pact-go)
09/01/2022, 11:12 PM
The Pactflow CLI tool
Matt (pactflow.io / pact-js / pact-go)
09/01/2022, 11:13 PM