Skip to content

feat(module-verification-report): show test results - #773

Merged
AlexanderLanin merged 1 commit into
mainfrom
feat/mvr-testlink-column
Aug 31, 2026
Merged

feat(module-verification-report): show test results#773
AlexanderLanin merged 1 commit into
mainfrom
feat/mvr-testlink-column

Conversation

@antonkri

Copy link
Copy Markdown
Contributor

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.

📌 Description

🚨 Impact Analysis

  • This change does not violate any tool requirements and is covered by existing tool requirements
  • This change does not violate any design decisions
  • Otherwise I have created a ticket for new tool qualification

✅ Checklist

  • Added/updated documentation for new or changed features
  • Added/updated tests to cover the changes
  • Followed project coding standards and guidelines

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.
@github-actions

Copy link
Copy Markdown
Contributor

License Check Results

🚀 The license check job ran with the Bazel command:

bazel run --lockfile_mode=error //src:license-check

Status: ⚠️ Needs Review

Click to expand output
[License Check Output]
Extracting Bazel installation...
Starting local Bazel server (8.6.0) and connecting to it...
INFO: Invocation ID: 6d448f29-bc9d-4e9d-ba82-5f68ea2f1800
Computing main repo mapping: 
Loading: 
Loading: 0 packages loaded
Loading: 0 packages loaded
Loading: 0 packages loaded
    currently loading: src
WARNING: Target pattern parsing failed.
ERROR: Skipping '//src:license-check': no such target '//src:license-check': target 'license-check' not declared in package 'src' defined by /home/runner/work/docs-as-code/docs-as-code/src/BUILD
ERROR: no such target '//src:license-check': target 'license-check' not declared in package 'src' defined by /home/runner/work/docs-as-code/docs-as-code/src/BUILD
INFO: Elapsed time: 6.373s
INFO: 0 processes.
ERROR: Build did NOT complete successfully
ERROR: Build failed. Not running target

@github-actions

Copy link
Copy Markdown
Contributor

Documentation preview for this pull request is available at:
pr-773: https://eclipse-score.github.io/docs-as-code/pr-773/

: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

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

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.

@AlexanderLanin

Copy link
Copy Markdown
Member

merging as-is for now, since initial template was also not reviewed. will address in next process meeting

@AlexanderLanin AlexanderLanin changed the title feat: show test results in module verification report feat(module-verification-report): show test results Aug 31, 2026
@AlexanderLanin
AlexanderLanin merged commit d66e8f3 into main Aug 31, 2026
20 of 21 checks passed
@AlexanderLanin
AlexanderLanin deleted the feat/mvr-testlink-column branch August 31, 2026 09:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

3 participants