feat(testcase): annotate testcase links with results

[AlexanderLanin]

Summary

• move testcase result annotations into score_source_code_linker
• decorate testcase backlinks with passed, failed, skipped, disabled, or fallback statuses

Extracted from #730; original author is @antonkri

---

see https://eclipse-score.github.io/docs-as-code/pr-739/internals/requirements/requirements.html

[github-actions]

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: a0a22c6c-a8e3-4b3c-aefa-385836e94909
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: 5.774s
INFO: 0 processes.
ERROR: Build did NOT complete successfully
ERROR: Build failed. Not running target

[github-actions]

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

[Copilot]

Pull request overview

This PR introduces a doctree-resolved post-processing hook in score_source_code_linker to annotate testcase links with a colored status badge derived from each testcase need’s result, and adds documentation + unit tests for the behavior.

Changes:

• Add testcase_annotations.py implementing annotate_testcase_results() to append (passed|failed|skipped|disabled|<other>) badges to testcase references.
• Register the new hook from the extension __init__.py and document the new module in extension docs.
• Add unit tests covering reference resolution via refid/refuri fragments and result-to-color mapping/fallback behavior.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/extensions/score_source_code_linker/tests/test_testcase_annotations.py	Adds unit tests for reference target resolution and result badge rendering.
src/extensions/score_source_code_linker/testcase_annotations.py	Implements doctree post-processing to append colored result badges to testcase references.
src/extensions/score_source_code_linker/init.py	Wires the new doctree-resolved hook into the extension setup.
src/extensions/docs/source_code_linker.md	Documents the presence/purpose of the new module file.
docs/how-to/test_to_doc_links.rst	Updates user documentation around test linking and describes testcase result annotations.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[Copilot]

Pull request overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated 4 comments.

[Copilot]

Pull request overview

Copilot reviewed 7 out of 7 changed files in this pull request and generated no new comments.

Suppressed comments (2)

Previously missed (2) — in code that hasn't changed since the last review.

docs/how-to/test_to_doc_links.rst:48

• This removes the only placement guidance for manually generated reports, but the linker does not discover arbitrary JUnit XML: it searches for files named test.xml under the workspace-root tests-report/ or Bazel's bazel-testlogs/. Without that detail, users of the advanced path cannot make the documented integration work.

This section is only relevant when your language or test framework does not
have one of the integrations above. In that case, produce JUnit XML with the
metadata described below. The generated test results are processed
automatically and create GitHub links from the requirements to the testcases.

.github/workflows/license_check.yml:42

• The composite action emits only one --comply-with flag, so this value expands to --comply-with ASF EF; the scanner consumes ASF as the policy and treats EF as another lockfile. The job will then try to parse a nonexistent EF file instead of checking both policies. Pass one policy here, or update the action to emit --comply-with once per policy.

          comply_with: ASF EF

[MaximilianSoerenPollak]

Overall looks okay I think.

It works in the implementation and rendered page and looks good.

[a-zw]

ASD-STE100 Simplified Technical English is a worthwhile guideline when writing how-tos.

[AlexanderLanin]

this talks about programming language

[MaximilianSoerenPollak]

Seems okay though still some questions open that can be adressed in future PRs.

Would like @a-zw approval too before merge.