BitzOrcas’s testing strategy follows the Vertical Slice approach — tests align with features/modules rather than technical layers. The project includes 5 test projects organized by testing concern.
Test projects
| Project | Purpose | Framework |
|---|---|---|
BitzOrcas.Unit.Tests | Domain logic, value objects, Result<T> | xUnit |
BitzOrcas.Application.Tests | Mediator handlers, pipeline behaviors | xUnit |
BitzOrcas.Integration.Tests | Full API tests with database | xUnit + WebApplicationFactory |
BitzOrcas.Architecture.Tests | Module boundary, DI registration, code conventions | NetArchTest |
BitzOrcas.CodeGeneration.Tests | Template rendering, code gen accuracy | xUnit |
Running tests
# Run all testsdotnet test
# Run specific projectdotnet test tests/BitzOrcas.Unit.Tests
# Run with coveragedotnet test --collect:"XPlat Code Coverage"Testing levels
| Level | What to test | Project |
|---|---|---|
| Unit | Domain logic, value objects, Result<T>, IRequestRule | Unit.Tests |
| Application | Mediator handlers, pipeline behaviors, mapping | Application.Tests |
| Integration | Full API pipeline with real DB | Integration.Tests |
| Architecture | Module boundaries, DI rules, naming conventions | Architecture.Tests |
See also
- Architecture tests — Module boundary verification
- Unit tests — Domain and unit testing patterns
- Integration tests — Full pipeline testing