pytest-coverage-gate-misleading-without-live-db
Running pytest with a coverage gate (e.g., --cov-fail-under=70) in an environment without live Postgres causes integration tests to auto-skip, artificially deflating the coverage percentage (66% observed vs 70% gate). The gate fires as a false failure in dev/CI environments without a DB service. The gate is correct behavior — the fix is to always attach a DB service in CI, not to lower the threshold.
Related
- db-free-test-coverage-drops-below-gate-without-postgres
- pytest-coverage-gate-skews-below-threshold-without-live-db
- r-dash-postgres-integration-tests-skip-on-creds
- r-dash-db-integration-tests-skip-on-postgres-creds-mismatch
- r-same-m1-identity-complete-frontend-integration-tests
- db-free-coverage-gate-understates-real-coverage
- db-free-coverage-gate-integration-test-skip-inflation
- coverage-gate-artificially-low-without-live-db