Add HTTP coverage for evidence link/unlink routes#3
Open
Mehrn0ush wants to merge 2 commits into
Open
Conversation
Restore skipped HTTP coverage for evidence link and unlink routes and add fixture setup for started assessment requirements. Signed-off-by: Mehrn0ush <mehrnoush.vaseghi@gmail.com>
Keep passing link and unlink coverage enabled and leave the unlink happy-path test skipped pending follow-up on current route behavior. Signed-off-by: Mehrn0ush <mehrnoush.vaseghi@gmail.com>
Up to standards ✅🟢 Issues
|
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.
Summary
This change adds HTTP test coverage for the evidence link and unlink
routes.
It restores coverage for the link route and for the unlink route's
authentication, permission, and missing-resource cases, using the current route
behavior already implemented in the backend.
What changed
Notes
The unlink happy-path test is intentionally left skipped for now.
While expanding this coverage, the unlink success path appeared to return
404even after a successful link, which looks like a separate follow-up item. This
PR keeps the scope narrow and focuses on the cases that already behave
consistently.
Related
Addresses #2