Hello, I have a question regardingn the UI and res...
# pactflowa
Aurelia
10/03/2022, 7:37 AMHello, I have a question regardingn the UI and results display.
Although the contracts are compatible, in the “overview” tab it still shows as “unknown.”
Any idea why ?
c
Candy Goodison
10/03/2022, 7:44 AMHi Aurelia Have you uploaded a verification for your provider? You can check in the provider contract tab
a
Aurelia
10/03/2022, 7:56 AMYes, this is what I have in the provider tab
c
Candy Goodison
10/03/2022, 8:00 AMThis section shows that it's unverified, you'll need to upload a verification result that indicates your oas contract is implemented by the API. https://docs.pactflow.io/docs/bi-directional-contract-testing/provider/
☝️ 1
m
Matt (pactflow.io / pact-js / pact-go)
10/03/2022, 8:13 AM
Yep, looks like You're missing the self verification results
a
Aurelia
10/03/2022, 9:08 AMok, indeed that step is currently missing, thanks for the prompt answer 🙂
👍 1
Aurelia
10/03/2022, 11:10 AMI struggle finding concrete example of this verification.
In my case, the OAS is generated automatically, thus I’d like to skip the verification and always publish a successful result for the verification step.
I found an example here : https://www.ontestautomation.com/an-introduction-to-contract-testing-part-6-bi-directional-contracts/, but I don’t know what structure should the verficationResults.content field have.
Can someone help me on this ?
m
Matt (pactflow.io / pact-js / pact-go)
10/03/2022, 12:04 PM
Just put something in there to indicate how you came to the conclusion it was safe
Matt (pactflow.io / pact-js / pact-go)
10/03/2022, 12:04 PM
it’s just an arbitrary field - I’d suggest “automatically generated by <tool>”
👍 1
n
Noor Hashem
10/03/2022, 5:03 PMWhen I wanted my provider contract to be verified just for a PoC stage I simply made a json file that was basically empty with only
{}Noor Hashem
10/03/2022, 5:03 PMThat seemed to work for me.
👍 2
a
Aurelia
10/04/2022, 6:33 AMYes this works as well