r-dash-postgres-integration-tests-skip-on-creds
Integration tests that require a live Postgres connection auto-skip or error with a DB auth/creds mismatch when run outside make up. This is a pre-existing environment issue (not a Wave 3 regression): 54 integration errors all share the same Postgres credentials failure mode. The 133 DB-free tests are the reliable CI signal; integration tests require make up with seeded Postgres to run.
Related
- r-dash-postgres-creds-mismatch-pre-existing-not-wave3-regres
- docker
- r-same-m1-identity-backend-core-wave-1-pass-1
- r-same-wave-0-scaffold-complete
- pytest-test-passwords-trigger-secret-scanner-false-positive
- postgres-creds-mismatch-causes-integration-test-skip-not-fai
- r-dash-db-integration-tests-skip-on-postgres-creds-mismatch
- pytest-coverage-gate-skews-below-threshold-without-live-db
- postgres-creds-mismatch-pre-existing-not-regression-marker
- db-free-test-coverage-drops-below-gate-without-postgres
- pytest-coverage-gate-misleading-without-live-db
- db-free-coverage-gate-understates-real-coverage
- db-free-coverage-gate-integration-test-skip-inflation