Alex Kuznetsov

this is a well known problem with mocking static functions - it affects the whole JVM, not just one thread. so, whenever tests happen to run in parallel with this...

we run kotest in gradle builds, and by default gradle runs different specs in parallel. So we can annotate `RealTest ` with `@DoNotParallelize` and see if that helps. Alternatively, we...

my understanding was that the following was being set under the hood: `system property kotest.framework.parallelism` So can you: * decorate your broken spec with `DoNotParallelize` annotation and see if it...

> Adding the annotation DoNotParallelize does not change anything. Then I was wrong, and this issue is not about parallel execution. Let's investigate more. Maybe: * `afterSpec` did not run...

returning to "Adding the annotation DoNotParallelize does not change anything" - I would expect that to fix the issue. This is where we should investigate further.

> I feel it's kind of ambiguous what we're looking at in the failure messages. Was it the wrong key or value? > > Perhaps we should produce a similarity-score...

> I feel it's kind of ambiguous what we're looking at in the failure messages. Was it the wrong key or value? > > Perhaps we should produce a similarity-score...

> @AlexCue987 Should this be refactored to use the similarity package now? of course, that's the plan. This will add more info to the output. No code will be removed,...

so the enhanced message should look like this: ``` shouldHaveMessage(""" |Collection should contain exactly: [Fruit(name=apple, color=green, taste=sweet), Fruit(name=apple, color=red, taste=sweet), Fruit(name=pear, color=green, taste=sweet)] but was: [Fruit(name=pear, color=green, taste=sweet), Fruit(name=apple, color=green,...

> There are conflicts on the merge. just resolved a redeclaration. did I miss any other conflicts?