Expense Database Testing Guide
Summary
Existing evidence includes migration and snapshot artifacts, development-seed guards, Expense smoke automation, compatibility parity automation, backfill validation and audit components, and a cutover runbook. No dedicated Expense database integration-test project is confirmed.
Audience
Backend developers, database reviewers, QA, architects, DevOps, support, and implementation teams.
Confirmed persistence
| Evidence | What is confirmed | What it does not prove |
|---|---|---|
| Migration classes and model snapshot | Ordered model evolution and the current expected EF model | Successful application in a production-like environment |
| Development seeder | Development-only guard and an idempotent marker around representative aggregate paths | Production migration or seed governance |
| Expense smoke script | Automated service smoke flow exists | Exhaustive database constraints, rollback, or concurrency behavior |
| Compatibility parity script | Automated comparison of compatibility and native behavior exists | Long-running synchronization or every historical data shape |
| Backfill validator and audit components | Dry-run, resume, invariant, count, and validation evidence is produced by the transition tooling | A completed production backfill |
| Cutover runbook | Go/no-go, validation, cutover, and rollback activities are documented operationally | Executed approval or successful rollback rehearsal |
No source-backed evidence was found for dedicated automated coverage of receipt cascade, tenant-filter bypass, transaction rollback across all tracked objects, concurrency, retention, or archival. Those remain test gaps rather than implied tests. Any execution must use approved isolated data and environments; this documentation workflow does not connect to a database.
Requires confirmation
Production migration governance, retention, archival, masking, performance targets, concurrency roadmap, operational-store access, and rollback ownership remain unconfirmed unless narrowed above.
Source References
microservices/scripts/smoke-expense.ps1microservices/scripts/compare-expense-parity.ps1microservices/src/expense-service/Backfill/ExpenseBackfillValidator.csmicroservices/docs/expense-cutover-runbook.md
Related Articles
See Also
Keywords
- Expense database
- Database Testing Guide
Revision Information
- Status: Draft
- Last reviewed: 2026-07-16
- Review cycle: Quarterly