feat(module-verification-report): show test results - #773
Merged
Conversation
The requirements tables of the module verification report listed the
backlinks `fully_verifies_back` and `partially_verifies_back`, which
render as bare need ids (e.g. `testcase__CheckBit__WithUInt8_gavap`).
That neither tells the reader whether a test passed nor links to the
test source.
Use the `testlink` option instead, which is populated by the
`test_code_linker` string link. It renders the test name together with
its result and links to the corresponding line in the test file. The
`doctree-resolved` hook `annotate_testcase_results` then colours the
`(passed|failed|skipped|disabled)` suffix.
Applied to both requirements tables:
- feature level ("Requirements Statistics", feat_req)
- component level ("Requirements Traceability", comp_req)
Verified against eclipse-score/baselibs: the report now renders 43
`(passed)` badges with clickable source links, up from none.
antonkri
requested review from
AlexanderLanin,
MaximilianSoerenPollak,
a-zw,
dcalavrezo-qorix and
nradakovic
as code owners
August 30, 2026 10:47
Contributor
License Check Results🚀 The license check job ran with the Bazel command: bazel run --lockfile_mode=error //src:license-checkStatus: Click to expand output |
Contributor
|
Documentation preview for this pull request is available at: |
| :style: table | ||
| :columns: id;title;safety;status;fully_verifies_back;partially_verifies_back | ||
| :colwidths: 13,22,8,10,23,24 | ||
| :columns: id;title;safety;status;testlink |
Contributor
There was a problem hiding this comment.
According to the title you want to show test results.
This will not just show test results, it will show the testlink of the requirement which will give you a link with the result tacked on at the end.
If that is what you want then this is correct, if you just want the results, you have to do this differently and most likely write some python code that gives you this in the return.
Member
|
merging as-is for now, since initial template was also not reviewed. will address in next process meeting |
AlexanderLanin
approved these changes
Aug 31, 2026
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.
The requirements tables of the module verification report listed the backlinks
fully_verifies_backandpartially_verifies_back, which render as bare need ids (e.g.testcase__CheckBit__WithUInt8_gavap). That neither tells the reader whether a test passed nor links to the test source.Use the
testlinkoption instead, which is populated by thetest_code_linkerstring link. It renders the test name together with its result and links to the corresponding line in the test file. Thedoctree-resolvedhookannotate_testcase_resultsthen colours the(passed|failed|skipped|disabled)suffix.Applied to both requirements tables:
Verified against eclipse-score/baselibs: the report now renders 43
(passed)badges with clickable source links, up from none.📌 Description
🚨 Impact Analysis
✅ Checklist