Closed sesamzoo closed 4 years ago
Good catch. I'll fix it
With upgrading to latest assertj-core release 3.18.0 this issue will be gone, because its StandardRepresentation
does
Honor toString if overridden in Iterable that are not collections.
Update: So, I guess #125 also fixed this issue.
That's true. It wasn't fixed in the project because of custom error message factories. I'll update them and will be fine
Description
50 hasn't completely fixed assertion error messages on
Either
, because of this line in assertj-core'sStandardRepresentation
:This might affect other assertion error messages, too.
Example
Expected Behavior
leads to an assertion error message containing the actual value, f.i. like
Actual Behavior
leads to assertion error message
Tested with