https://pact.io logo
Join Slack
Powered by
What it means unknown status in pactflow though pa...
# pactflow
s
What it means unknown status in pactflow though pact are compatible in bidirectional
m
Can you please show a screenshot of the UI?
s
Here it is
m
Can you please click through to the next page with the details?
s
message has been deleted
message has been deleted
m
So the answer is right there - you need to set a status for the self verification
see these flags:
Copy code
--verification-exit-code=EXIT_CODE \
  --verification-results REPORT_PATH \
  --verification-results-content-type REPORT_CONTENT_TYPE \
  --verifier VERIFIER
s
Without ci/cd pipelines without make file need to pass these from commandline
m
Sorry, I’m not sure what you’re asking? These are flags on the CLI command, you can call that command through any means (makefile, bash script, docker command etc.)
s
if i pass 0 tests are getting passed or 1 for failed it should be dynamic
✅ 1
I am on private repositories and trying to config github actions not displaying workflows as in public repositories
Thanks for your patience to my questions
👍 1
m
What's the script you're using to call the CLI?
s
Running from my terminal
m
Thanks. How are you calling it from your terminal? It seems you might be missing some arguments, which is why the status is “unknown”
If you set the status to passing or failing, that would change what you see in Pactflow
Currently, it says “the documents are compatible, but we don’t know if the provider implements the OAS”
s
I have generated swagger.yaml file
m
that’s fine, but those arguments still need to be set
s
I need exactly where our verification tests between consumer contract and provider oas/yaml file happening and arguments that return pass/ fail after verification
m
The verification happens when you publish the provider contract. The cli I shared above has flags you need to set when you do that.
It also happens when can I deploy is called for comparisons that werent previously pre computed. The point is, when you publish the pact file it the verification results should happen then. In your case you are generating the OAS and not testing it with a tool (you should probably also do that), so you can just set the result to success and specify an empty file as the results
s
In your example of bidirectional with postman as provider where test is happening with a tool please point me with in your example
Also please let us know additional features and support we get from pactflow on licensed veraion
m
s
Thank you I think its happening cross contract validation process
👍 1
2 Views
Open in Slack
PreviousNext
Powered by