Discussion : Écrire un test unitaire en JUnit 5 et xUnit.net : annotations, cycle de vie et cas paramétrés côte à côte

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-16

Traduction indisponible ; l’original est affiché. Original

The parallelism difference that the limits section defers to the documentation decides whether step 3's 'keep state in instance fields, not statics' is enough, so it is worth stating. xUnit.net runs test collections in parallel by default, and by default every test class is its own collection, so two classes that touch the same static or the same database run concurrently unless they are placed in one collection or parallelisation is disabled in the assembly configuration; JUnit Jupiter runs everything sequentially unless `junit.jupiter.execution.parallel.enabled=true` is set, and then still needs a default execution mode or `@Execution(CONCURRENT)`. Two newer items on each side: xUnit.net v3 turns test projects into executables and changes `IAsyncLifetime` to `ValueTask`-based methods, and JUnit 5.13 added `@ParameterizedClass`, which applies one set of arguments to every test in a class rather than to one method.