Skip to content

SPRDT-874: Adjournment CROWN journey updates#318

Open
ragubalan wants to merge 4 commits into
team/ccsph2from
dev/SPRDT-874
Open

SPRDT-874: Adjournment CROWN journey updates#318
ragubalan wants to merge 4 commits into
team/ccsph2from
dev/SPRDT-874

Conversation

@ragubalan

@ragubalan ragubalan commented May 21, 2026

Copy link
Copy Markdown
Contributor

Jira link

See https://tools.hmcts.net/jira/browse/SPRDT-874

Change description

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?

  • Yes
  • No

Checklist

  • commit messages are meaningful and follow good commit message guidelines
  • README and other documentation has been updated / added (if needed)
  • tests have been updated / new tests has been added (if needed)
  • Does this PR introduce a breaking change

@ragubalan ragubalan requested a review from a team as a code owner May 21, 2026 10:13
@ragubalan ragubalan requested review from JayalakshmiParthiban, danielwilsonkainos and kumarsajan1983 and removed request for a team May 21, 2026 10:13
@cpp-github-management

Copy link
Copy Markdown

Passed

ozturkmenb and others added 2 commits June 13, 2026 18:39
…-as-courtScheduleId behaviour

Crown next hearings with a bookingReference absent from the provisional booking
slots map use the bookingReference itself as the courtScheduleId rather than
warning and skipping. Update the NHCC test to assert that behaviour and add a
separate NHMC (Magistrates) test confirming the warn-and-skip path is unchanged
for non-Crown jurisdictions.
@cpp-github-management

Copy link
Copy Markdown

Passed

@ozturkmenb

Copy link
Copy Markdown
Contributor

Integration test run — dev/SPRDT-874 @ 7b86518

Ran locally via ./runIntegrationTests.sh (full stack: WildFly + PostgreSQL + Artemis + Elasticsearch), clean container start, mvn clean first.

progression-integration-test (Failsafe)

Metric Count
Tests run 351
Failures 2
Errors 0
Skipped 8
Suite time 22:35 min
Total build 23:19 min

Failures — both unrelated to this PR

This PR's change is confined to HearingToHearingListingNeedsTransformer tests + UnscheduledCourtHearingListTransformer. The two failing IT classes are in unrelated domains (representation-order messaging, defendant ingester) and do not exercise the listing-needs / Crown bookingReference path:

  1. ReceiveRepresentationOrderForApplicationIT.shouldRaisePublicEventWhenApplicationIsFoundForReceiveRepresentationOrderForApplicationWithOrganisation
    verifyInMessagingQueueForApplication:181Expected: is <true> but: was <false> (JMS public-event queue assertion; looks like an awaitility timing flake).
  2. ProsecutionCaseDefendantUpdatedIngesterIT.shouldUpdateDefendant:74.

This PR's coverage passed

The changed unit suite ran green:

  • HearingToHearingListingNeedsTransformerTest32 tests, 0 failures, 0 errors, 0 skipped.

The upstream surefire (unit) layers all reported Failures: 0. Recommend a re-run of the two flaky ITs to confirm they go green on a clean stack; they are not caused by this change.

@ozturkmenb

Copy link
Copy Markdown
Contributor

Re-run (full suite) — dev/SPRDT-874 @ 7b86518

Same flow as above: clean containers → mvn clean./runIntegrationTests.sh on a fresh stack.

Metric Run 1 Run 2 (re-run)
Tests run 351 351
Failures 2 1
Errors 0 0
Skipped 8 8
Build time 23:19 min 23:12 min

Outcome per failure

  • ProsecutionCaseDefendantUpdatedIngesterIT.shouldUpdateDefendant — passed on re-run → confirmed flaky.
  • ReceiveRepresentationOrderForApplicationIT.shouldRaisePublicEventWhenApplicationIsFoundForReceiveRepresentationOrderForApplicationWithOrganisation — failed again at verifyInMessagingQueueForApplication:181 (Expected: is <true> but: was <false>).
    • Reproducible across both runs → not a random flake. Looks like a pre-existing / environmental issue with the public-event queue assertion in the local IT stack.
    • Still unrelated to this PR: the change is test-only, this IT is not part of SPRDT-874: Adjournment CROWN journey updates #318, and it does not exercise the listing-needs / Crown bookingReference path.

This PR's coverage

  • HearingToHearingListingNeedsTransformerTest32 tests, 0 failures, 0 errors, 0 skipped (green on both runs).

Net: the only remaining red is a deterministic, pre-existing failure outside this change's scope; worth a separate look but does not block this PR's logic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants