Skip to content

CI: backend tests run without running DB migrations or provisioning a database #761

Description

@Cedarich

Problem
CI workflows do not run database migrations or provide a database service before running backend integration/e2e tests. This leads to failing tests or false negatives in CI.

Evidence

  • Repo contains Rust/TypeScript backend and database-related SQL/PLpgSQL files; no CI workflow for migrations detected.

How to reproduce

  1. Run backend test pipeline in a fresh environment without DB migrations — tests fail or are skipped.

Suggested fix

  • Add a postgres service to CI workflow and run migrations (e.g., prisma migrate deploy or Diesel migrations) before tests.
  • Use a test DB URL injected via environment variables and secret management.

Files to check

  • .github/workflows/**
  • backend/migrations or prisma/
  • ci scripts

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Stellar WaveIssues in the Stellar wave program

Type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions