Closed jdsika closed 3 months ago
I suggest, that OSI validation should run on every test (integration and behavior). So as soon as an input trace file is used in a test, osi-validation shall automatically check it against the input. And as soon as an output trace file is generated by a test, osi-validation shall automatically check it against the output rules. So OSI validation becomes sort of a meta test of every test.
Therefore, I will wait with the implementation for https://github.com/openMSL/sl-1-0-sensor-model-repository-template/pull/77 to be merged. Then I will directly implement it for both CL2 and CL3 tests.
Idea: 3 kinds of rule sets:
The official ASAM rules are auto-generated by osi-validation
The repository rules shall be defined for the input and output and put in the doc folder alongside a requirements description.
Individual test rules shall be placed in the corresponding test folder. The pipeline shall automatically detect the rules folder for a test and run osi-validation on the test results with the defined rules.
Release is out: https://github.com/OpenSimulationInterface/osi-validation