Repository Docs & Knowledge Base

Consolidated Spensara documentation repository (722 Markdown & architecture documents in ../repository)

Branch-specific documentation across extract-raw-xml, feature-fleet-import, kds_cdc_improvments, life-cycle, and tenat-admin.

branches/life-cycle/agent-tooling/backend/tests/AGENTS.md 1,798 bytes · Updated Oct 23, 2026 10:44 AM EDT

Raw File

Backend Tests

These rules apply to everything under backend/tests/.

Use xUnit everywhere.
Use [Fact] for single-case tests and [Theory] with [InlineData(...)] for parameterized tests.

Prefer native Xunit.Assert for new tests.
Keep assertions direct and readable.
Assert the behavior that matters most: output, persisted state, ordering, filtering, and errors.

Tests must be deterministic and independent.
Do not rely on execution order.
For API/data tests, keep per-test isolation through the provided schema/fixture infrastructure.
Do not share mutable state between tests unless it is explicitly managed by an xUnit fixture.

Reuse existing test infrastructure in Infrastructure/ before adding new helpers.
For Kds.Ai.ApiService.Tests, use the shared PostgreSQL/Testcontainers fixture pattern already present.
If a test requires Docker/Testcontainers, make that dependency explicit and keep the test focused.

Run tests with dotnet test --project <path-to-test-csproj>.
Prefer validating one backend test project at a time.
After test changes, run the relevant dotnet test --project ... command.
If backend code was changed together with tests, finish with a solution build when possible.
Do not run dotnet build and dotnet test at the same time for overlapping backend projects.
Do not run multiple build/test commands in parallel against the same project outputs because file locks can cause false failures.