test-credential-literals-flagged-by-secret-scanner

Integration test files with hardcoded password strings (even obviously fake ones like ‘Test@12345678’) are flagged by the pre-commit secret scanner and block commits. The fix is to assign them to clearly named constants (e.g., TEST_PASSWORD = ’…’) so the scanner recognises the test-fixture context. Apply this pattern when writing any test that uses credential literals.

Related

• integration-test-passwords-flag-secret-scanner
• secret-scanner-flags-test-passwords-use-labeled-constants
• secret-scanner-flags-test-passwords-without-constant-label
• test-password-strings-trigger-secret-scanner-false-positives
• alembic-ini-db-url-triggers-secret-scanner-on-commit
• test-fixture-passwords-flagged-by-secret-scanner
• pytest-hardcoded-passwords-trigger-secret-scanner
• pytest-test-passwords-trigger-secret-scanner-false-positive