-
Notifications
You must be signed in to change notification settings - Fork 377
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
AssertionError message is unhelpful when match fails for byte type #254
Comments
jamesmudd
added a commit
to jamesmudd/JavaHamcrest
that referenced
this issue
Apr 17, 2019
This was referenced Apr 29, 2021
This was referenced May 12, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Here is an example of a JUnit 5 test displaying this issue:
From
testShort
the error message is good: (Note: <5s>)But from
testByte
you get:Which looks ok
<5>
is<5>
! Of course the reason the failed is the types are mismatched so the failure is correct, but it would be good to show this more clearly in the message.The text was updated successfully, but these errors were encountered: