CADB-184: Fix Failing Integration Tests in SJP for Java 25 Upgrade - #159
Open
KarthikaRenjith1 wants to merge 1 commit into
Open
KarthikaRenjith1 wants to merge 1 commit into
KarthikaRenjith1 wants to merge 1 commit into
Conversation
KarthikaRenjith1
requested review from
SeemaSajan,
ZaheerIqbal-HMCTS and
aykutdanisman
and removed request for
a team
September 28, 2026 12:57
KarthikaRenjith1
changed the title
|
|
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.
Jira link
https://hmcts.atlassian.net/browse/CADB-184
See PROJ-XXXXXX
Change description
CaseUnassignmentIT/AssignmentRulesIT
issues: Tests failed intermittently with ConditionTimeoutException in AssignmentHelper- assignment/ unassignment was requested immediately after case creation, before the case's read model row was confirmed ready, racing the eventually projection.
Fix
Added CaseHelper.pollUntilCaseReady(caseId) before the assignment step, using the same readiness-polling pattern already used elsewhere in the suite. Test only change no production code touched.
Testing done
Security Vulnerability Assessment
CVE Suppression: Are there any CVEs present in the codebase (either newly introduced or pre-existing) that are being intentionally suppressed or ignored by this commit?
Checklist