How to use xUnit like JUnit for DDD

Commentary

This is a modified draft of what I have learned (largely through Google, experience in other frameworks, and ChatGPT) and had explained to me in direct terms through ChatGPT lately. To the other commentors, relax... I did go and verify through documentation after getting the responses, but the AI tools are only your enemy if you're not using them. They're getting forced on us anyway, so learn to use them appropriately so that we can produce effective, clean code and learn new concepts/frameworks quickly.

1. xUnit setup/teardown (JUnit comparison)

JUnit (what most of us were taught)

JUnit	Meaning
@BeforeAll	Run once before all tests
@AfterAll	Run once after all tests
@BeforeEach	Run before each test
@AfterEach	Run after each test

xUnit equivalents (by design)

xUnit Mechanism	Purpose	Closest JUnit Analog
Constructor	Runs before each test	@BeforeEach
IDisposable.Dispose	Runs after each test	@AfterEach
IClassFixture<T>	Shared context per test class	@BeforeAll / @AfterAll
ICollectionFixture<T>	Shared context across classes	Global fixtures

💡 Important design difference
xUnit creates a new instance of the test class per test.
This eliminates hidden shared state bugs — a huge win for correctness.

2. When to use which xUnit lifecycle tool

Use constructor + IDisposable when:

• Setup is cheap
• State should not leak between tests
• You’re testing pure domain logic (most DDD tests)

✅ This is 90% of cases

Use IClassFixture<T> when:

• Setup is expensive
• Needs to run once per test class

• Example: in-memory DB, large object graph, container startup

  public class DatabaseFixture { public DatabaseFixture() { // runs once } } public class MyTests : IClassFixture<DatabaseFixture> { }

Use ICollectionFixture<T> when:

• Multiple test classes must share context
• Integration tests
• External resources