Performance Database Testing Guide
Summary
Existing persistence test evidence and clearly separated recommended coverage.
Audience
Backend engineers, database reviewers, architects, QA, support, operations, security reviewers, and product owners.
Overview
The repository has a broad Performance smoke script and backfill parity helpers. No dedicated Performance .NET unit or database integration test project exists.
Confirmed persistence behavior
- Existing smoke coverage exercises migrations in a local development flow, seed behavior, aggregate/child persistence, history creation, outbox side effects, Workflow references, reports, compatibility CRUD, Gateway routing, backfill, resume behavior, and parity checks.
- Backfill validation compares source and target counts and aggregate totals.
- No dedicated repository integration, migration rollback, tenant-filter bypass, transaction rollback, cascade deletion, processed-event, concurrency, or messaging-persistence test suite was found.
- Recommended tests should use isolated disposable persistence and synthetic data; production systems are out of scope.
- Recommended suites remain Foundation: domain persistence, repository integration, migrations, tenant isolation, transaction boundaries, messaging persistence, compatibility, and backfill/parity.
Classification
Transitional evidence: broad smoke coverage but missing dedicated automated persistence suites.
Requires confirmation
CI ownership, isolated test provisioning, coverage thresholds, destructive-test controls, migration gates, and concurrency expectations require confirmation.
Related Articles
See Also
Keywords
- Performance persistence
- Database Testing Guide
- Draft database documentation
Source References
microservices/scripts/smoke-performance.ps1microservices/src/performance-service/Backfill/PerformanceBackfillSmokeSupport.csmicroservices/src/performance-service/Backfill/PerformanceBackfillValidator.csmicroservices/src/performance-service/performance-service.csproj
Revision Information
- Status: Draft
- Last reviewed: 2026-07-16
- Review cycle: Quarterly