Telegram (ask questions / claim the issue here first): https://t.me/+DOylgFv1jyJlNzM0
Labels: bug, Stellar Wave
Backend integration tests fail on main because there's no PostgreSQL database for tests/integration/stream-lifecycle.test.ts to connect to.
Running npm test in the backend package errors out with Prisma connection failures:
Can't reach database server at 127.0.0.1:5432
The test explicitly uses a real Postgres db and falls back to postgresql://postgres:password@127.0.0.1:5432/flowfi_test when DATABASE_URL isn't set. On the GitHub Actions runner nothing is listening there, so CI is red on the default branch. Reproduces locally too if you don't have a test db configured.
What the fix has to hold to
- Backend suite passes on
main
- Integration tests either get a real db or are gated so they don't fail when one isn't available
Done when
Where to start
Look at the backend CI workflow and tests/integration/stream-lifecycle.test.ts. A Postgres service container in the workflow (plus the right DATABASE_URL) is the usual fix. Scope is CI config plus maybe test setup, not the streaming logic.
Labels:
bug,Stellar WaveBackend integration tests fail on
mainbecause there's no PostgreSQL database fortests/integration/stream-lifecycle.test.tsto connect to.Running
npm testin the backend package errors out with Prisma connection failures:The test explicitly uses a real Postgres db and falls back to
postgresql://postgres:password@127.0.0.1:5432/flowfi_testwhenDATABASE_URLisn't set. On the GitHub Actions runner nothing is listening there, so CI is red on the default branch. Reproduces locally too if you don't have a test db configured.What the fix has to hold to
mainDone when
DATABASE_URLis set correctly in CI, or db-dependent tests are gated behind explicit setupWhere to start
Look at the backend CI workflow and
tests/integration/stream-lifecycle.test.ts. A Postgres service container in the workflow (plus the rightDATABASE_URL) is the usual fix. Scope is CI config plus maybe test setup, not the streaming logic.