-
-
Notifications
You must be signed in to change notification settings - Fork 481
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
Improve junit output on test failure due to MissingStateChangeMethod #1112
Comments
anto-ac
pushed a commit
to anto-ac/pact-jvm
that referenced
this issue
Jun 11, 2020
…me to output when an expected state change cannot be found
anto-ac
pushed a commit
to anto-ac/pact-jvm
that referenced
this issue
Jun 11, 2020
…ame to output when an expected state change cannot be found
uglyog
pushed a commit
that referenced
this issue
Jun 11, 2020
…ge-output feat: #1112 add interaction description and consumer name to output wh…
anto-ac
pushed a commit
to anto-ac/pact-jvm
that referenced
this issue
Jun 14, 2020
…e for missing state change
uglyog
pushed a commit
that referenced
this issue
Jun 14, 2020
…te-change feat: #1112 junit5: print interaction and consumer name for missing s…
This is done for both junit4 and junit5 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, when a test fails due a
MissingStateChangeMethod
, it is impossible to know which pact and interaction the state originates from. Neither the stacktrace nor the standard output mention anything that helps. You need to go and find the state somewhere, which can be difficult when there is more than one consumer.It would ideal if, at least, the consumer name was included and, perhaps, which interaction(s) are involved.
Current stacktrace
Current standard output
The text was updated successfully, but these errors were encountered: