r-dash-postgres-creds-mismatch-pre-existing-not-wave3-regression
DB-dependent integration tests fail with auth errors because Postgres is listening but has a credentials mismatch in the test environment. This is a pre-existing condition from before Wave 3 — not a regression. DB-free tests (133) remain the reliable baseline.
Related
- pytest-test-passwords-trigger-secret-scanner-false-positive
- docker
- pytest-hardcoded-passwords-trigger-secret-scanner
- r-same-m1-identity-complete-frontend-integration-tests
- alembic-ini-db-url-triggers-secret-scanner-on-commit
- r-dash-postgres-integration-tests-skip-on-creds
- 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