integration-test-passwords-flag-secret-scanner

Plaintext credential strings in pytest integration test files (e.g., password='Correct-Horse-Battery-Staple!') trigger the secret scanner hook even in clearly named test files. The fix is to move them into a labeled constant at the top of the file (e.g., TEST_ADMIN_PASSWORD = '...') so the scanner’s pattern-matcher recognizes test-only context. Apply this pattern to any new test file that needs credential fixtures.

Related

• secret-scanner-flags-test-passwords-use-labeled-constants
• test-password-strings-trigger-secret-scanner-false-positives
• secret-scanner-flags-test-passwords-without-constant-label
• spec-reviewer-blocks-on-os-system-in-test-code
• security-hook-blocks-exec-eval-tokens-in-prose
• test-credential-literals-flagged-by-secret-scanner
• test-fixture-passwords-flagged-by-secret-scanner
• pytest-hardcoded-passwords-trigger-secret-scanner
• pytest-test-passwords-trigger-secret-scanner-false-positive