| name | overview-drn-testing |
| description | DTT (Duran's Testing Technique) philosophy - choosing unit, integration, API, or performance tests and routing to canonical DRN.Framework.Testing guidance. Keywords: testing-philosophy, dtt, test-strategy, unit-testing, integration-testing, performance-testing |
| last-updated | "2026-06-12T00:00:00.000Z" |
| difficulty | basic |
| tokens | ~0.7K |
DRN Testing Overview
DTT favors honest feedback with the least necessary test machinery. The canonical attribute/context matrix lives in drn-testing.
DTT Principles
| Principle | Practice |
|---|
| Security first | Avoid leaking secrets in fixtures, logs, snapshots, and generated data |
| Correctness over speed | Prefer real dependencies when mocks would hide behavior |
| Clarity over cleverness | One readable flow beats many tiny duplicate tests |
| Simplicity | Use [Fact] when no data, generation, or context is needed |
| Performance with proof | Benchmark only when a performance question is explicit |
Test Type Selection
| Change | Default test type | Why |
|---|
| Pure utility, domain invariant, deterministic branch logic | Unit | No container value; use DataInlineUnit when data/generation helps |
| Attribute DI registration or isolated service behavior | Unit | DrnTestContextUnit validates wiring without Docker |
| Repository, EF mapping, query, transaction, concurrency | Integration DB | Real PostgreSQL is the useful signal |
| Controller, endpoint, auth, middleware, serialization | API integration | Full request pipeline via ApplicationContext |
| External HTTP client behavior | Integration/API | Use FlurlHttpTest against outbound URL patterns |
| Throughput, allocation, latency, load | Performance | BenchmarkDotNet/K6 only with explicit user intent |
Project Shape
DRN.Test.Unit/ # isolated logic and service validation
DRN.Test.Integration/ # Testcontainers, repositories, API/E2E
DRN.Test.Performance/ # BenchmarkDotNet and K6
Context names:
DrnTestContextUnit: unit context, no containersDrnTestContext: integration context with ContainerContext, ApplicationContext, and FlurlHttpTestApplicationContext: WebApplicationFactory wrapper for app/API tests
Routing
