test: add missing unit test for maxConsecutiveCharacters (OKTA-1228272) - #1702
Open
prachi-okta wants to merge 1 commit into
Open
test: add missing unit test for maxConsecutiveCharacters (OKTA-1228272)#1702prachi-okta wants to merge 1 commit into
prachi-okta wants to merge 1 commit into
Conversation
…TA-1228272) The maxConsecutiveCharacters field was added to PasswordPolicyPasswordSettingsComplexity in #1699, but never got a dedicated regression test. Add one covering both directions: a caller value is no longer silently dropped on deserialization, and it's correctly included on serialization. Co-Authored-By: Claude Code
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Issue(s)
Closes a test-coverage gap on OKTA-1228272 (already fixed in #1699, but never got a dedicated unit test).
Description
Auditing all Java SDK bug tickets assigned to the reporter (per the OKTA-1228xxx series) for fix + test completeness turned up one gap:
maxConsecutiveCharacterswas added toPasswordPolicyPasswordSettingsComplexityin #1699, but no test verified it round-trips correctly (neither that it's populated on deserialization, nor that it's included on serialization).Adds
PasswordPolicyPasswordSettingsComplexityTestcovering both directions.Category
Signoff
AI Attribution:
ai-agent-authored