secret-scanner-flags-test-passwords-without-constant-label

Integration test files that contain plain password strings (e.g. 'AdminPass123!') trigger the secret scanner and block commits. The workaround is to assign them to a labeled constant (e.g. TEST_PASSWORD = 'AdminPass123!') so the scanner recognises them as test fixtures rather than credential leaks.

Related

• spec-reviewer-blocks-on-os-system-in-test-code
• r-same-auth-constant-time-generic-errors-required
• dual-claude-json-sync-invariant-session-user-determines-acti
• r-dash-azure-ad-deferred-local-auth-v1-stack
• alembic-ini-db-url-blocks-commit-use-env-var
• test-password-strings-trigger-secret-scanner-false-positives
• 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