pytest-test-passwords-trigger-secret-scanner-false-positive
Hardcoded test password strings in pytest fixtures (e.g., ‘TestPassword123!’) trigger the secret scanner even in test files. Fix: extract them to a clearly labeled constant (e.g., TEST_PASSWORD = ‘TestPassword123!’) so the scanner recognizes them as intentional test fixtures rather than leaked credentials. Apply this pattern to all integration test conftest.py files.
Related
- pytest-hardcoded-passwords-trigger-secret-scanner
- integration-test-passwords-flag-secret-scanner
- test-fixture-passwords-flagged-by-secret-scanner
- test-credential-literals-flagged-by-secret-scanner
- secret-scanner-flags-test-passwords-use-labeled-constants
- r-dash-postgres-creds-mismatch-pre-existing-not-wave3-regres
- r-dash-postgres-integration-tests-skip-on-creds
- postgres-creds-mismatch-causes-integration-test-skip-not-fai