Skip to content

HDPI-3344: set invalid fee register url for negative testing#1620

Open
benouaer wants to merge 4 commits intomasterfrom
HDPI-3344-fee-lookup-failure-testing
Open

HDPI-3344: set invalid fee register url for negative testing#1620
benouaer wants to merge 4 commits intomasterfrom
HDPI-3344-fee-lookup-failure-testing

Conversation

@benouaer
Copy link
Copy Markdown

@benouaer benouaer commented Apr 2, 2026

Jira link

Change description

  • set invalid fee register url for negative testing

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

@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 2, 2026

CCD diff summary

👉 Full report: https://github.com/hmcts/pcs-api/actions/runs/23909431296?check_suite_focus=true

No change

java:
environment:
FEES_REGISTER_API_URL: "https://wiremock-${SERVICE_NAME}.preview.platform.hmcts.net"
FEES_REGISTER_API_URL: "https://invalid-fee-register-url.preview.platform.hmcts.net"
Copy link
Copy Markdown
Contributor

@tvr-hmcts tvr-hmcts Apr 2, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wondering if there is another approach that could be take to this. Still using the configured SERVICE_NAME but applying different wiremock stubs to return the relevant HTTP codes to mimic the behaviour required?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this was done as a quick and dirty change to enable manual negative testing
if we want to create an automated test for this, we should definitely configure the appropriate wiremock response
plus, the thing we're trying to mimic here is the service being down

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants