Show actual failing assert message when using nested e.g. satisfiesExactlyInAnyOrder

[HerrDerb]

In an assertion, I am using satisfiesExactlyInAnyOrder with a list of asserts.

When a assertion fails, I am only getting the exception message of the top assertions on which satisfiesExactlyInAnyOrder is called. I Have to manually search for the culprit assertion within the satisfiesExactlyInAnyOrder.

Am I doing something wrong? Due to using inner asserts, assertJ should know exactly which assertion has failed. It seems that the cause of an inner assertion is not being reflected in the top failing assertion exceptions tacktrace/message

assertThat(myListWithUncannyObjects).satisfiesExactlyInAnyOrder( 
     item ->  assertThat(item.value).isEqualTo(1),
     item ->  assertThat(item.value).isEqualTo(2),
     item ->  assertThat(item.value).isEqualTo(3), // assume this assert is failing
     item ->  assertThat(item.value).isEqualTo(4),

will result in

Expecting actual:
%myListWithUncannyObjects as string%
to satisfy all the consumers in any order.

Which inner assertion that actually has failed, I don't know, although the cause would be propagated

[joel-costigliola]

This could be a nice improvement indeed, FTR you get a better error message if you can use satisfiesExactly since it reports the failing assertions.

[HerrDerb]

satisfiesExactly requires a predictable order, which I do not have.

So you are saying the desired implementation is already existent in satisfiesExactly but not yet in satisfiesExactlyInAnyOrder ?

[joel-costigliola]

yes, what is a bit trickier with satisfiesExactlyInAnyOrder is that we would need to report the assertions that failed for all the elements (it would not be just one assertion for one element)

[HerrDerb]

Ah yes, I see 😅 Most likely only the assertions should be reported that threw as many times as the count of processed items