Skip to content
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

Include interaction description in verification results #292

Closed
gregtyler opened this issue Jun 15, 2023 · 3 comments
Closed

Include interaction description in verification results #292

gregtyler opened this issue Jun 15, 2023 · 3 comments
Labels
smartbear-supported SmartBear engineering team will support this issue. See https://docs.pact.io/help/smartbear

Comments

@gregtyler
Copy link

The verification results published from the Rust verifier are extremely streamlined, containing only the interaction ID, success boolean and any mismatches. This is easier to parse than the old verification results, which contained a myriad of data even if the test was successful.

However, interaction IDs are not an easy way of understanding which test failed, as they must then be cross-referenced with a separate document to track them back to the test in code.

To make this easier, could you add the interaction description to the verification results too? This would make it much easier to get a quick understanding of what's broken from the results themselves.

@rholshausen
Copy link
Contributor

The verification results format is defined by the Pact broker project. I think it will just ignore additional fields, but I am waiting on conformation of that.

@rholshausen rholshausen added the smartbear-supported SmartBear engineering team will support this issue. See https://docs.pact.io/help/smartbear label Feb 19, 2024
Copy link

🤖 Great news! We've labeled this issue as smartbear-supported and created a tracking ticket in PactFlow's Jira (PACT-1839). We'll keep work public and post updates here. Meanwhile, feel free to check out our docs. Thanks for your patience!

@JP-Ellis
Copy link
Contributor

JP-Ellis commented Jun 3, 2024

Closing this as @rholshausen appears to have implemented the issue and the internal ticket has been marked is done :)

@JP-Ellis JP-Ellis closed this as completed Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
smartbear-supported SmartBear engineering team will support this issue. See https://docs.pact.io/help/smartbear
Projects
None yet
Development

No branches or pull requests

4 participants