Mihály Verhás

This is the same issue I encountered in [this PR (#664)](https://github.com/junit-pioneer/junit-pioneer/pull/664). You pass a `Comparator

I think this can be solved by removing the type arguments of the `Comparator` passed to `usingComparator`. This shouldn't lead to any issue (I think?) because it's used to create...

I don't like `@Silenced` - to me that communicates that the test is silenced _regardless of outcome_, which misses point 3 from the list (a succeeding test is marked failed)....

I've been thinking about this the last couple of days. Unfortunately I'm not really familiar with the multithreading in Java. 😔 I've been reading up a bit and I think...

I have something that I have no idea how to test. 😅 But if it works then it was a lot easier then I expected, since I can just let...

Hi @bartsimp! Unfortunately, I don't have a lot of time right now, but I wanted to call your attention to this issue: https://github.com/junit-pioneer/junit-pioneer/issues/639 Your problem is in the JSON file.

Hm, I'm not a 100% sure that an annotation is the proper place for what is essentially an [assumption](https://junit.org/junit5/docs/current/user-guide/#writing-tests-assumptions). We should consider providing this functionality in the form of a...

I had a lame idea that I think is worth considering: keeping a manual changelog. I can already hear the masses gasping in terror, "manually doing a task that could...

I don't think it makes the user choose? By default it's always test-scoped with an optional configuration option to make it class scoped.

Also I don't know what this means: > but make the extension additionally visible in @BeforeAll. How do you want to achieve that?