1.x Use IntelliJ IDE friendly assertion failure message #5258
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The

assertItem
failure message pattern inTestSubscriber
does not match any of the regex patterns defined by IntelliJ to show<Click to see difference>
link.By changing the "expected to be" to "expected:", the pattern is recognised by IntelliJ and the helpful link is presented.

The original idea from #5249 was to use the "expected:<> but was:<>" pattern used in JUnit, but it is not picked up on its own by IntelliJ. The AssertionError must extend from JUnit's ComparisonFailure, to get it recognised. This however requires dependency on JUnit.

So in the end, the fix is just a very simple change in the message.