From 6aa755917447f5b2840a39e345c24d944ac95410 Mon Sep 17 00:00:00 2001 From: "jhr2hi@bosch.com" Date: Mon, 26 Oct 2026 10:54:04 +0100 Subject: [PATCH 1/3] improvement update test levels --- .../guidance/verification_process_reqs.rst | 44 +++++++++++-------- .../verification/verification_concept.rst | 10 +++-- .../verification/verification_workflows.rst | 8 ++-- 3 files changed, 36 insertions(+), 26 deletions(-) diff --git a/process/process_areas/verification/guidance/verification_process_reqs.rst b/process/process_areas/verification/guidance/verification_process_reqs.rst index c9cd7cfb698..c7b72ba4cee 100644 --- a/process/process_areas/verification/guidance/verification_process_reqs.rst +++ b/process/process_areas/verification/guidance/verification_process_reqs.rst @@ -20,7 +20,7 @@ Process Requirements .. gd_req:: Linking Requirements to Tests :id: gd_req__verification_link_tests :status: valid - :version: 1 + :version: 2 :tags: prio_1_automation, verification :satisfies: wf__verification_unit_test[version==1], wf__verification_comp_int_test[version==1], @@ -29,25 +29,23 @@ Process Requirements :complies: std_req__iso26262__support_6432[version==1] - For linking test suites to requirements following metadata shall be used: + For linking test suites to requirements following metadata shall be used. Each field may contain multiple + comma-separated values from the applicable levels below: * Verifies * PartiallyVerifies * FullyVerifies * Description * TestType - * Fault Injection (fault-injection) - * Interface Test (interface-test) - * Requirements-based Test (requirements-based) - * Resource Usage Evaluation (resource-usage) + * Interface Test (interface-test): unit, component, feature + * Requirements-based Test (requirements-based): component, feature, platform * DerivationTechnique - * Analysis of requirements (requirements-analysis) - * Analysis of design (design-analysis) - * Analysis of boundary values (boundary-values) - * Analysis of equivalence classes (equivalence-classes) - * Fuzzy testing (fuzz-testing) - * Error guessing based on knowledge or experience (error-guessing) - * Explorative testing (explorative-testing) + * Analysis of requirements (requirements-analysis): all levels + * Analysis of boundary values (boundary-values): component, feature, platform + * Analysis of equivalence classes (equivalence-classes): all levels + * Fuzzy testing (fuzz-testing): unit, component, feature + * Error guessing based on knowledge or experience (error-guessing): all levels + * Explorative testing (explorative-testing): all levels More information can be found in the :need:`gd_guidl__verification_guide`, :need:`doc_concept__verification_process`, @@ -179,7 +177,7 @@ Process Requirements .. gd_req:: Verification Documentation Checks :id: gd_req__verification_checks :status: valid - :version: 1 + :version: 2 :tags: prio_1_automation, verification :satisfies: wf__verification_unit_test[version==1], wf__verification_comp_int_test[version==1], @@ -191,10 +189,20 @@ Process Requirements - TestType and DerivationTechnique shall be set - Description shall not be empty - - In a Platform Integration Test Partially/FullyVerifies shall be set to at least one Platform Requirement - - If Partially/FullyVerifies are set in Feature Integration Test these shall link to at least one Feature Requirement or Architectural element - - If Partially/FullyVerifies are set in Component Integration Test these shall link to at least one Component Requirement or Architectural element - - If Partially/FullyVerifies are set in Unit Test these shall link to at least one Component Requirement + + 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`` + - ``score/.*/tests/`` (Component): ``comp``, ``comp_req``, ``comp_arc_dyn``, ``comp_arc_sta``, ``real_arc_int``, ``real_arc_int_op`` + - Anything else (Unit): ``comp_req``, ``feat_req`` + + The minimum link coverage shall also be enforced: + + - Platform Integration Tests shall link to at least one stakeholder requirement. + - If Partially/FullyVerifies are set in a Feature Integration Test, these shall use one or more allowed Feature links. + - If Partially/FullyVerifies are set in a Component Integration Test, these shall use one or more allowed Component links. + - If Partially/FullyVerifies are set in a Unit Test, these shall use one or more allowed Unit links. .. gd_req:: Verification Documentation Checks Extended :id: gd_req__verification_checks_extended diff --git a/process/process_areas/verification/verification_concept.rst b/process/process_areas/verification/verification_concept.rst index 6f05409f673..30777695c3c 100644 --- a/process/process_areas/verification/verification_concept.rst +++ b/process/process_areas/verification/verification_concept.rst @@ -126,7 +126,9 @@ The rigor is described in the implementation of :need:`wp__verification_plan`. 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 +:need:`gd_req__verification_link_tests`. Other verification methods described here remain applicable, but their +identifiers are not supported as *TestType* or *DerivationTechnique* values. Test Case Development ===================== @@ -155,9 +157,9 @@ Following aspect should be considered when developing test cases: General Traceability Concept ============================ -To allow a traceability of code to a written requirement, unit tests are linked to other unit -tests or component tests. This linking is done using metatags. This is also true for component -integration tests linking to the component requirements and architecture. +To allow a traceability of code to a written requirement, unit tests use ``Verifies`` links to component or feature +requirements as allowed by :need:`gd_req__verification_checks`. They may also link to related unit or component tests. +Component integration tests link to the component requirements and architecture as allowed by the same requirement. Traceability of feature integration tests shall be established through linking those test cases to feature requirements and architecture as features describe the integrated behavior of all components. diff --git a/process/process_areas/verification/verification_workflows.rst b/process/process_areas/verification/verification_workflows.rst index cebef53885b..08280920caf 100644 --- a/process/process_areas/verification/verification_workflows.rst +++ b/process/process_areas/verification/verification_workflows.rst @@ -29,7 +29,7 @@ For a detailed explanation of workflows and their role within the process model, :supported_by: rl__safety_manager[version==1] :input: wp__sw_implementation[version==1], wp__verification_plan[version==1] :output: wp__verification_sw_unit_test[version==1] - :contains: gd_req__verification_link_tests[version==1], + :contains: gd_req__verification_link_tests[version==2], gd_req__verification_link_tests_cpp[version==1], gd_req__verification_link_tests_python[version==1], gd_req__verification_link_tests_rust[version==1], @@ -71,7 +71,7 @@ For a detailed explanation of workflows and their role within the process model, wp__requirements_comp_aou[version==1], wp__verification_plan[version==1] :output: wp__verification_comp_int_test[version==1] - :contains: gd_req__verification_link_tests[version==1], + :contains: gd_req__verification_link_tests[version==2], gd_req__verification_link_tests_cpp[version==1], gd_req__verification_link_tests_python[version==1], gd_req__verification_link_tests_rust[version==1], @@ -103,7 +103,7 @@ For a detailed explanation of workflows and their role within the process model, wp__requirements_feat_aou[version==1], wp__verification_plan[version==1] :output: wp__verification_feat_int_test[version==1] - :contains: gd_req__verification_link_tests[version==1], + :contains: gd_req__verification_link_tests[version==2], gd_req__verification_link_tests_cpp[version==1], gd_req__verification_link_tests_python[version==1], gd_req__verification_link_tests_rust[version==1], @@ -128,7 +128,7 @@ For a detailed explanation of workflows and their role within the process model, :supported_by: rl__safety_manager[version==1] :input: wp__requirements_stkh[version==1], wp__verification_plan[version==1] :output: wp__verification_platform_int_test[version==1] - :contains: gd_req__verification_link_tests[version==1], + :contains: gd_req__verification_link_tests[version==2], gd_req__verification_link_tests_cpp[version==1], gd_req__verification_link_tests_python[version==1], gd_req__verification_link_tests_rust[version==1], From 63bb863eaa429e8814e40c8b30c894ffb20280eb Mon Sep 17 00:00:00 2001 From: "jhr2hi@bosch.com" Date: Thu, 29 Oct 2026 13:08:15 +0100 Subject: [PATCH 2/3] revert deletion of test methods --- .../verification/guidance/verification_process_reqs.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/process/process_areas/verification/guidance/verification_process_reqs.rst b/process/process_areas/verification/guidance/verification_process_reqs.rst index c7b72ba4cee..28ee9e10c65 100644 --- a/process/process_areas/verification/guidance/verification_process_reqs.rst +++ b/process/process_areas/verification/guidance/verification_process_reqs.rst @@ -37,17 +37,19 @@ Process Requirements * FullyVerifies * Description * TestType + * Fault Injection (fault-injection) * Interface Test (interface-test): unit, component, feature * Requirements-based Test (requirements-based): component, feature, platform + * Resource Usage Evaluation (resource-usage) * DerivationTechnique * Analysis of requirements (requirements-analysis): all levels + * Analysis of design (design-analysis) * Analysis of boundary values (boundary-values): component, feature, platform * Analysis of equivalence classes (equivalence-classes): all levels * Fuzzy testing (fuzz-testing): unit, component, feature * Error guessing based on knowledge or experience (error-guessing): all levels * Explorative testing (explorative-testing): all levels - More information can be found in the :need:`gd_guidl__verification_guide`, :need:`doc_concept__verification_process`, and :need:`gd_guidl__verification_specification` . From 4210c5a439fcd88aebec95e8d56e287c373b201f Mon Sep 17 00:00:00 2001 From: "jhr2hi@bosch.com" Date: Thu, 29 Oct 2026 14:36:44 +0100 Subject: [PATCH 3/3] fix review findings --- .../verification/guidance/verification_process_reqs.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/process/process_areas/verification/guidance/verification_process_reqs.rst b/process/process_areas/verification/guidance/verification_process_reqs.rst index 28ee9e10c65..5a3c8e41f1e 100644 --- a/process/process_areas/verification/guidance/verification_process_reqs.rst +++ b/process/process_areas/verification/guidance/verification_process_reqs.rst @@ -37,13 +37,13 @@ Process Requirements * FullyVerifies * Description * TestType - * Fault Injection (fault-injection) + * Fault Injection (fault-injection): unit, component, feature * Interface Test (interface-test): unit, component, feature * Requirements-based Test (requirements-based): component, feature, platform - * Resource Usage Evaluation (resource-usage) + * Resource Usage Evaluation (resource-usage): feature * DerivationTechnique * Analysis of requirements (requirements-analysis): all levels - * Analysis of design (design-analysis) + * Analysis of design (design-analysis): all levels * Analysis of boundary values (boundary-values): component, feature, platform * Analysis of equivalence classes (equivalence-classes): all levels * Fuzzy testing (fuzz-testing): unit, component, feature