there are tests that sometimes very rarely fail an...
# strikt
c
there are tests that sometimes very rarely fail and it stays a mystery why they do. i wonder if it makes sense to have support for outputting more diagnostic output in that case
Copy code
expectThat(totalEvents).containsExactly(
                    listOf("first test", "second close callback", "first close callback"),
                    listOf("second test", "second close callback", "first close callback"),
                ).onFailure {.... }
thats one assertion from my testing library that fails every month or so.
and when it fails i get some ideas of values i could output in that case.
for example if its threading related it could be interesting if 100ms later the values finally is as expected