add example for auto generated module verification report - #166
add example for auto generated module verification report#166RolandJentschETAS wants to merge 5 commits into
Conversation
License Check Results🚀 The license check job ran with the Bazel command: bazel run --lockfile_mode=error //:license-checkStatus: Click to expand output |
|
Documentation preview for this pull request is available at: |
| # tooling | ||
| bazel_dep(name = "score_tooling", version = "1.2.0", dev_dependency = True) | ||
| bazel_dep(name = "aspect_rules_lint", version = "1.10.2", dev_dependency = True) | ||
| bazel_dep(name = "aspect_rules_lint", version = "2.3.0", dev_dependency = True) |
There was a problem hiding this comment.
There was a warning regards to that... If I made a PR I can fix that together.
There was a problem hiding this comment.
aspect_rules_lint was set directly by this template’s MODULE.bazel in 1dd74ec (bazel_dep(..., version = "2.3.0")). The resolved lockfile also shows aspect_tools_telemetry 0.2.8 requesting 2.3.0; no separate module update caused it.
There was a problem hiding this comment.
@copilot yeah, but this was done only to resolve a warning. So what other module did the update?
There was a problem hiding this comment.
It was score_bazel_cpp_toolchains 1.0.3. Its MODULE.bazel declares aspect_rules_lint 2.3.0 (alongside score_tooling 1.1.2), while score_tooling 1.2.0 itself requests 1.5.3.
Co-authored-by: Alexander Lanin <Alexander.Lanin@etas.com> Signed-off-by: RolandJentschETAS <135332348+RolandJentschETAS@users.noreply.github.com>
| :id: doc__mod_temp_verification_report | ||
| :status: draft | ||
| :version: 1 | ||
| :safety: ASIL_B | ||
| :security: NO | ||
| :realizes: wp__verification_module_ver_report | ||
| :tags: template |
There was a problem hiding this comment.
Does this even work with this formating?
There was a problem hiding this comment.
Yes, as long as the indentation is same.
See https://eclipse-score.github.io/module_template/pr-166/verification_report/module_verification_report.html
|
|
||
| The verification report is generated automatically by the codeblock above by the tools and contains all the needed information for the module verification. The report is based on the module verification plan and covers all the components of the module. | ||
|
|
||
| The generated report should contain the following parts: |
There was a problem hiding this comment.
Should we mention / link here to the need template that actually builds all this information and where changes can be made if something is missing / not right etc. ?
@AlexanderLanin @RolandJentschETAS
There was a problem hiding this comment.
Is this a need template ? I though thats a python script, what generates this.
There was a problem hiding this comment.
It's both, but the actual content comes from a need template it can be found here
There was a problem hiding this comment.
nope, no python, just https://github.com/eclipse-score/docs-as-code/tree/main/src/needs_templates
There was a problem hiding this comment.
I link into the source code sounds strange for me, but I can add the link if wanted.
There was a problem hiding this comment.
I mean that is where the template is defined.
That where is you have to change it.
This pull request updates the documentation examples and module verification report templates to improve clarity, completeness, and traceability between logical interfaces and their implementing components. The changes provide more detailed descriptions of logical interfaces, their mapping to components and sub-components, and clarify the structure and content of module verification reports.
Documentation and Example Improvements:
That fixes "FIXME Warnings"
Module Verification Report Template Enhancements:
Other Minor Updates: