Repository navigation
improvement update test levels - #853
Open
RolandJentschETAS wants to merge 3 commits into
Open
RolandJentschETAS wants to merge 3 commits into
RolandJentschETAS wants to merge 3 commits into
Conversation
RolandJentschETAS
requested review from
PandaeDo,
aschemmel-tech,
masc2023 and
pahmann
as code owners
October 29, 2026 13:39
|
The created documentation from the pull request is available at: docu-html |
| Automated test cases (as well as manual, where applicable) shall contain further information about which methods have been applied. | ||
| The corresponding guidance is given here: :need:`gd_guidl__verification_guide`. | ||
| The identifier of the respective method is to be used as meta data (*TestType* and *DerivationTechnique*). | ||
| For Sphinx-Needs test metadata, use only the identifiers and test levels listed in |
Member
There was a problem hiding this comment.
process should not mention specific tools?!
pahmann
reviewed
Oct 30, 2026
| The test level is determined by the test's folder path. Verifies links shall use only the allowed types for that level: | ||
|
|
||
| - ``platform_integration_tests/`` (Platform): ``stkh_req`` | ||
| - ``score/tests/`` (Feature): ``feat``, ``feat_req``, ``feat_arc_dyn``, ``feat_arc_sta``, ``mod``, ``mod_view_dyn``, ``mod_view_sta``, ``tool_req`` |
Member
There was a problem hiding this comment.
Do we really play it that hard and make it mandatory?
Will it work with the idea that feature integration test can live in the reference integration and in the feature repository (we discussed this for better linking and testing depending on whether they link to architecture or requirements )
| * Resource Usage Evaluation (resource-usage) | ||
| * Fault Injection (fault-injection): unit, component, feature | ||
| * Interface Test (interface-test): unit, component, feature | ||
| * Requirements-based Test (requirements-based): component, feature, platform |
Member
There was a problem hiding this comment.
I remember we discussed that a unit test can also cover some part of requirement, but maybe as it already uses linking other requirements it automatically transfers into a component level test.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request updates the requirements and guidance for linking tests to requirements and clarifies the allowed metadata for test cases at different verification levels. The main changes include stricter definitions for test metadata, explicit mapping of allowed link types per test level, and updates to documentation to ensure consistency across the verification process.
Process requirements and metadata guidance updates:
Linking Requirements to TestsandVerification Documentation Checksrequirements (gd_req__verification_link_testsandgd_req__verification_checks) are updated to version 2, reflecting stricter and more detailed guidance for linking tests to requirements. [1] [2]TestTypeandDerivationTechniquenow specify which test levels (unit, component, feature, platform) each value applies to, and fields may contain multiple comma-separated values.Verifieslinks are now explicitly defined for each test level, determined by folder structure, and minimum coverage requirements are enforced for each level.Documentation and workflow consistency:
gd_req__verification_link_testsrequirement, ensuring process consistency. [1] [2] [3] [4]