Skip to content

Add local test execution for manual or automated tests to verification process area #481

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
PandaeDo merged 3 commits into from
Dec 19, 2025
Merged

Add local test execution for manual or automated tests to verification process area #481

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
3f2e9ba
Add manual testing to verification plan template
pahmann Dec 2, 2025
65c9f86
Add manual test execution to verification guide and concept
pahmann Dec 19, 2025
2f47a0b
should shall be shall
pahmann Dec 19, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 9 additions & 0 deletions process/process_areas/verification/guidance/verification_guideline.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -96,9 +96,18 @@ In order to check the test results for the impact of a change or addition, it is
execute affected test cases locally upfront using the execution framework of the build tooling
following basically the steps the CI does locally.

Automated tests can also be executed locally, as the sources and binaries are available for re-execution.
Failing test cases during re-execution can be reported following the guide :need:`gd_temp__problem_template`.


Execution of manual test cases
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

There may be the need for limited number of manually executed test cases.
These manually executed test cases are execution script driven, where a script guides through the
test cases and reports the result in the same logging format as automated tests do.
This enables parsable execution logs which can be used in automated test result collection.
Failing test cases during manual execution are reported by following the guide :need:`gd_temp__problem_template`.

Reporting of failing test cases
-------------------------------
Expand Down
6 changes: 6 additions & 0 deletions process/process_areas/verification/guidance/verification_plan_template.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -150,6 +150,12 @@ Verification Plan Template
This section describes how tests will be executed and the procedures for analyzing the results.
It should outline the tools and processes used for test execution and reporting.

Manual test execution
^^^^^^^^^^^^^^^^^^^^^

The automation rate for test case execution is expected to be above 99%.
For manual test execution it should be described how to re-execute tests manually and how to report potential issues.

Test Selection and Regression Testing
-------------------------------------

Expand Down
2 changes: 1 addition & 1 deletion process/process_areas/verification/verification_concept.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -124,7 +124,7 @@ Also their execution may differ whether it is a QM or ASIL rated test case.
The rigor is described in the implementation of :need:`wp__verification_plan`.


Automated test cases should contain further information about which methods have been applied.
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*).

Expand Down
Loading