fix: bot detection test unit test #1232
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tanya732
approved these changes
Nov 3, 2025
kushalshit27
deleted the
SDK-6856d-fix-test-public-api-for-bot-detection
branch
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
This PR fixes failing tests in
attack-protection.test.tsby updating the bot detection challenge policy values to use the correct enum values.Updated the test data in
test/management/attack-protection.test.tsto use proper enum values for bot detection challenge policies:challenge_passwordless_policyfrom'high_risk'to'when_risky'challenge_password_reset_policyfrom'off'to'never'Ref: #1213
Testing
npm test)Related
Fixes test failures in the bot detection test suite.
Checklist