-
Notifications
You must be signed in to change notification settings - Fork 36
Add docker-compose integration test harness #63
Copy link
Copy link
Open
Labels
Stellar WaveIssues in the Stellar wave programIssues in the Stellar wave programarea:ciCI/CD and toolingCI/CD and toolingarea:testsTesting and coverageTesting and coveragedifficulty:intermediate~half a day~half a dayhelp wantedExtra attention is neededExtra attention is needed
Description
Metadata
Metadata
Assignees
Labels
Stellar WaveIssues in the Stellar wave programIssues in the Stellar wave programarea:ciCI/CD and toolingCI/CD and toolingarea:testsTesting and coverageTesting and coveragedifficulty:intermediate~half a day~half a dayhelp wantedExtra attention is neededExtra attention is needed
Background
Unit tests mock the database. Real bugs (migrations, index usage, transaction isolation) surface only against a real Postgres. A docker-compose-based integration suite that spins up Postgres + the Wraith API and runs end-to-end queries catches those.
What to build
A
docker-compose.test.ymlthat brings up Postgres + Wraith, atests/integration/directory with Vitest specs that hit the running API, and a CI job that runs them on every PR.Key files
docker-compose.test.ymltests/integration/.github/workflows/ci.ymlSuggested execution
docker-compose.test.ymlbrings up Postgres on a deterministic port + the Wraith APItests/integration/setup.tsthat seeds known fixtures/transfers,/accounts/:address/summaryetc.docker compose -f docker-compose.test.yml up -d, thennpm run test:integrationExample commit message:
test(integration): add docker-compose harness and integration test suiteAcceptance criteria
docker compose -f docker-compose.test.yml upbrings up the stacknpm run test:integrationruns cleanly on a fresh machine