test-password-strings-trigger-secret-scanner-false-positives
Hardcoded password strings in pytest test files (e.g., ‘TestPass123!’) trigger secret scanner hooks even in obvious test contexts, blocking commits. Fix: assign to a named module-level constant (TEST_PASSWORD = ‘TestPass123!’) so scanners recognize the token as a labeled test fixture rather than an accidentally committed credential.
Related
- secret-scanner-flags-test-passwords-without-constant-label
- alembic-ini-hardcoded-db-url-triggers-secret-scanner
- spec-reviewer-blocks-on-os-system-in-test-code
- r-same-auth-constant-time-generic-errors-required
- claude-desktop-connector-no-static-bearer-auth
- secret-scanner-flags-test-passwords-use-labeled-constants
- integration-test-passwords-flag-secret-scanner
- test-credential-literals-flagged-by-secret-scanner
- test-fixture-passwords-flagged-by-secret-scanner
- pytest-hardcoded-passwords-trigger-secret-scanner