If JUnit is present, FEST-Assert creates a ComparisonFailure instead of an AssertionError. In this case, the error message is formatted as follows:
A Test expected:<[Yoda]> but was:<[Luke]>
but it is expected to be:
[A Test] expected:<'Yoda'> but was:<'Luke'>
I just found out that ComparisonFailure adds brackets to the expected and actual values to indicate the differences between these two values.
The expected error message when JUnit is present should be:
[A Test] expected:<'[Yoda]'> but was:<'[Luke]'>
Bug
Resolved
Minor
Error message when comparing Strings is not consistent between JUnit and TestNG
I just found out that ComparisonFailure adds brackets to the expected and actual values to indicate the differences between these two values.