What
Only 3 integration tests exist today. Expand to at least 15 scenarios covering transactions, concurrency, failure modes, and backend parity across PostgreSQL and SQLite.
- Current: 3 integration tests
- Expected: >=15 scenarios, parameterized per backend
- Scope:
tests/integration/**
Why
- Integration gaps cause regressions when switching backends
- ACID correctness claims need multi-backend proof
How
Technical Approach
- Draft a scenario matrix: CRUD, transactions (commit/rollback), isolation levels, connection loss, schema migration
- Use
testcontainers-cpp (or docker-compose) for PostgreSQL
- Parameterize GTest to run each case on both backends
- Add workflow
.github/workflows/integration.yml
Acceptance Criteria
What
Only 3 integration tests exist today. Expand to at least 15 scenarios covering transactions, concurrency, failure modes, and backend parity across PostgreSQL and SQLite.
tests/integration/**Why
How
Technical Approach
testcontainers-cpp(or docker-compose) for PostgreSQL.github/workflows/integration.ymlAcceptance Criteria
docs/testing/SCENARIOS.md