Granular verification feedback on view pact page? #170
Comments
|
How good would that be - PR's welcome :) |
|
You've read my mind Tim ;-) I'm working on a format to push the test results back to the broker already. The slight complication is that the pact version will likely have many verifications, and from different tags. So we need a way to select which verification results we want. I'm imagining a drop down from which we can select the tag name, the latest regardless of tags, or the latest untagged. |
|
That'll be really great! |
|
Not for future readers - this has been implemented in pactflow.io |
YOU54F
pushed a commit
to YOU54F/pact_broker
that referenced
this issue
Jul 31, 2024
* feat: adding support for share success and failure actions * Merging latest 'main' changes in to Action Object Extensions branch (pact-foundation#170) * chore: suggest multilevel parameters (pact-foundation#155) * chore: suggest multilevel parameters * Update versions/1.0.0.md Co-authored-by: Frank Kilcommins <fkilcommins@gmail.com> * Update examples/1.0.0/ExtendedParametersExample.workflow.yaml Co-authored-by: Frank Kilcommins <fkilcommins@gmail.com> * Update versions/1.0.0.md Co-authored-by: Frank Kilcommins <fkilcommins@gmail.com> --------- Co-authored-by: Frank Kilcommins <fkilcommins@gmail.com> * Remove references to WHATWG to avoid confusion (pact-foundation#145) * Remove references to WHATWG to avoid confusion * Correct relative reference wording * Section 4.2 not 4.1! * Simplify URI wording * Adjust Step Parameters desc to cater for Workflow parameters addition (pact-foundation#169) * feat: add `dependsOn` capability for workflow level (pact-foundation#164) * feat: add `dependsOn` capability for workflow level * chore: typo fix * chore: grammer fix * feat: Add Request Body Object (pact-foundation#162) * feat: Add Request Body Object * chore: fix typos in examples * Clarity on referencing Components Parameters (pact-foundation#149) * Clarity on referencing Components Parameters * Remove Reference Object to avoid clash with JSON Schema keyword. Replace with expression based referencing * chore: keep fixed field link names consistent * chore: Name component parameters as type Reusable Parameter Object * chore: adjust Workflow level parameters to use Reusable Parameter Objects --------- Co-authored-by: Dmytro Anansky <dmytro@redocly.com> Co-authored-by: Nick Denny <nick@apimetrics.com> * Add Reusable Object and referencing ability * chore: fix yaml example indentation * chore: fix JSON examples * chore: fix typo in `workflowStepActions` --------- Co-authored-by: Dmytro Anansky <dmytro@redocly.com> Co-authored-by: Nick Denny <nick@apimetrics.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be particularly excellent if the view pact page had granular feedback on which request/response pairs are failing verification.
Even something simple like colouring the background:
would be valuable.
The text was updated successfully, but these errors were encountered: