verification improvements (inconsistencies)

[pahmann]

Test properties:

• ASIL -> Any need for this or is the test case linking to requirements sufficient
• Status -> do we need valid/invalid, if the frameworks have options to disable tests from execution like "disabled_" before test case name in googletest and "@pytest.skip" before the test function.
  https://docs.pytest.org/en/stable/reference/reference.html#pytest-skip

Will properties be allocated to a need which will have the properties as attribute.

Properties are fixed values and need to be checked by tooling.
Can we link from within test case as we have done this as comment.
The test case results

Test specification does not include ASIL_B / QM. Do we need it as part of test specification.
Security is not a checked property yet.

Properties are currently not checked which need to be modified so that Test type and derivation technique as examples are recorded for every test case.

Pie charts (or tables) for test status: valid, type, derivation as three charts.
This could be a parsing of xml and link from the docu. When you will build the docu you have an old result

[AlexanderLanin]

Meeting Minutes

2025-06-25
@aschemmel-tech, @AlexanderLanin, @MaximilianSoerenPollak

• properties: basically free text is sufficient, but evaluations should be
  possible in the future

• Metrics about TestType and DerivationTechnique should be possible in the distant
  future. As overall statistics, not as statements per requirement - for that,
  they can be looked at individually.

• Goal is a table
  | req-1 | fully covered by A |
  | req-2 | partially covered by A, B, C |

• Remove ASIL property

• Description: What should the test actually do? Since they are usually not
  readable. As a property or as a docstring, doesn't matter. No import to sphinx
  needed.

• -> test-cases don't have to be needs