fix: Update tool requirements & update to process 2.0.2#659
fix: Update tool requirements & update to process 2.0.2#659MaximilianSoerenPollak wants to merge 2 commits into
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 |
| Docs-as-Code shall check if linked needs have different versions, compared to | ||
| the version the need was originally linked to. |
There was a problem hiding this comment.
Parent gd_req__req_suspicious says:
Based on the requirement versioning it shall be checked if a requirement was updated but not the linked tests. In case an update was detected the attribute complete test coverage shall be set to “No”
I don't see how we cover this at all? This tool_req__docs_common_attr_suspicious is not about tests and it also sounds more general going beyond just tests.
| Docs-as-Code shall set the ``testcovered`` attribute (see | ||
| :need:`tool_req__docs_req_attr_testcov`) of a requirement to ``No`` whenever | ||
| :need:`tool_req__docs_req_testlink_outdated_check` detects that a linked test is | ||
| outdated with respect to the requirement's version. |
There was a problem hiding this comment.
I don't like this requirement. This would be very confusing for users, if the testcovered attribute in HTML is different than in the source rst.
📌 Description
Updates to newest process release, and adapts one tool requirement and expands it so it covers the new process req version
🚨 Impact Analysis
✅ Checklist