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

Failing provider test still produces OK response to broker #1715

Closed
kevindeboer opened this issue Sep 7, 2023 · 0 comments
Closed

Failing provider test still produces OK response to broker #1715

kevindeboer opened this issue Sep 7, 2023 · 0 comments
Labels
bug Indicates an unexpected problem or unintended behavior

Comments

@kevindeboer
Copy link

Hi, we are setting up consumer driven testing in our pipelines, and we are trying to replicate a scenario where the provider test fails. I do this by simply asserting 1 equals 2 in the test function. But I dont understand why there is still an OK result being sent to the broker.
image

Strangely enough, if the test fails through an exception thrown by context.verifyInteraction(), we get a proper Failed result sent to the broker. However, if an exception is thrown by the assertion below it, we get an OK result sent to the broker.
image

@rholshausen rholshausen added the bug Indicates an unexpected problem or unintended behavior label Sep 21, 2023
@github-project-automation github-project-automation bot moved this from New Issue to Closed in Pact Triage (not yet in use) Dec 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Indicates an unexpected problem or unintended behavior
Projects
Status: Closed
Development

No branches or pull requests

2 participants