4499 add controller tests for high priority untested modules - #4628
Open
DeboraSerra wants to merge 7 commits into
Open
4499 add controller tests for high priority untested modules#4628DeboraSerra wants to merge 7 commits into
DeboraSerra wants to merge 7 commits into
Conversation
…99-add-controller-tests-for-high-priority-untested-modules
…ction in the trust centre network test
✅ Coverage Gate PassedAll coverage thresholds are met. |
MuhammadKhalilzadeh
requested changes
Sep 8, 2026
MuhammadKhalilzadeh
left a comment
Collaborator
There was a problem hiding this comment.
Thank you @DeboraSerra
Let's fix the failing github checks as well
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
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.
Describe your changes
Six of the seven controllers named here already had passing suites, so this covers the real
gaps: a new advisor.ctrl.ts suite (73 tests; SSE streaming excluded) and branch top-ups on
fileManager and approvalRequest. On the frontend, existing error tests asserted against a bare thrown Error, so the MSW error scaffold now spans six domains with 25 tests using the real
{ message, data }envelope. Two findings for reviewers: the scaffold's envelope was inverted and is fixed here; getFileErrorMessage branches onstatusCodewhile apiServices throws.status, so those branches are dead — pinned by tests, left unfixed as it changes user-facing copy.Write your issue number after "Fixes "
Fixes #4499
Please ensure all items are checked off before requesting a review:
npm run generate:swagger).authenticateJWTand the generated spec declaresbearerAuthsecurity.npm run check:api-driftand committed the regeneratedswagger.yamlandendpoints.ts.