CCD-7472: Add BEFTA tests for document filtering against saved case data#2908
Merged
Conversation
Adds two scenarios to F-1003 covering the CDAM/CCD sync fix: - S-1045: the about-to-submit callback strips the document supplied in the payload - the document must not be persisted to the case (regression test for the production incident shape) - S-1046: the about-to-submit callback echoes the data unchanged - the document must still be persisted (guards the new saved-data filter against over-filtering) Both use the FT_MasterCaseType documentHashCallback creation event with metadata-scoped dynamic wiremock stubs on the ccd-test-stubs service, following the S-1041 pattern. The CDAM-side assertion (attach not invoked) is covered by CaseDetailsEndpointIT in this PR, as BEFTA cannot observe CDAM calls black-box.
…id shared-wiremock cross-talk
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
2 participants
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.
Adds two scenarios to F-1003 covering the CDAM/CCD sync fix:
Both use the FT_MasterCaseType documentHashCallback creation event with metadata-scoped dynamic wiremock stubs on the ccd-test-stubs service, following the S-1041 pattern. The CDAM-side assertion (attach not invoked) is covered by CaseDetailsEndpointIT in this PR, as BEFTA cannot observe CDAM calls black-box.
Before creating a pull request make sure that:
keep-helmlabel has been added, if the helm release should be persisted after a successful buildPlease remove this line and everything above and fill the following sections:
JIRA link (if applicable)
Change description
Does this PR introduce a breaking change? (check one with "x")