docs: rewrite test_to_doc_links how-to for C++, Rust, and Python#549
Conversation
License Check Results🚀 The license check job ran with the Bazel command: bazel run --lockfile_mode=error //src:license-checkStatus: Click to expand output |
|
The created documentation from the pull request is available at: docu-html |
AlexanderLanin
left a comment
There was a problem hiding this comment.
AI-assisted review (Claude):
Severity breakdown: Critical: 0, Important: 1, Suggestions: 1
Nice rewrite — the structure is much clearer and the language-specific guidance with cross-references to requirements is a solid improvement over the old Python-only example.
One accuracy issue with the Description property claim (see inline comment) and one minor discoverability note about a dropped cross-reference to dashboards_and_quality_gates. The old doc had a "Related" section linking there — might be worth keeping as a brief "See also" since it covers end-to-end dashboard and CI threshold setup, which is a natural next step after setting up test links.
The two external need references (gd_guidl__verification_specification, gd_temp__verification_specification) appear to resolve correctly in the PR preview build, so those look fine.
See https://eclipse-score.github.io/docs-as-code/pr-549/how-to/test_to_doc_links.html