pytest-hardcoded-passwords-trigger-secret-scanner

Hardcoded password strings in pytest test fixtures trigger the pre-commit secret scanner even when clearly within a test file. The fix is to extract them to named constants (e.g., TEST_PASSWORD = ‘Test@1234!’) so the scanner recognizes them as labeled test fixtures rather than leaked credentials. Apply this pattern to all auth integration tests in R-Same.

Related

• integration-test-passwords-flag-secret-scanner
• test-credential-literals-flagged-by-secret-scanner
• secret-scanner-flags-test-passwords-use-labeled-constants
• test-fixture-passwords-flagged-by-secret-scanner
• test-password-strings-trigger-secret-scanner-false-positives
• pytest-test-passwords-trigger-secret-scanner-false-positive
• r-dash-postgres-creds-mismatch-pre-existing-not-wave3-regres