bdd-dotnet

BDD-style unit tests for .NET domain handlers use Given_When_Then naming conventions with NUnit, real repositories backed by EF Core InMemory databases, and TestDataBuilder patterns to validate domain logic end-to-end without mocks or external dependencies.

Yes. EF Core InMemory databases enable realistic validation of command and query handlers by providing a real repository layer that exercises domain logic, workflow transitions, and aggregate interactions without requiring external services.

Use the TestDataBuilder pattern to orchestrate reusable test fixtures and fluent Aggregate Builders to construct domain objects in a readable, expressive style that aligns with Given_When_Then semantics and Arrange-Act-Assert structure.

No. Fake implementations for clocks, unit of work, and services isolate the unit under test without mocks, while real repositories backed by EF Core InMemory validate domain logic authentically without external dependencies.

Structure tests using Given_When_Then naming conventions with Arrange-Act-Assert patterns. The framework provides naming conventions, test structure examples, and TestDataBuilder orchestration to align unit tests with BDD semantics.

Yes. The hybrid testing approach with real repositories and EF Core InMemory enables testing workflow transitions, aggregate interactions, and complex domain logic by exercising the full handler pipeline with realistic data.