adopt verification report - #330
Conversation
License Check Results🚀 The license check job ran with the Bazel command: bazel run --lockfile_mode=error //:license-checkStatus: Click to expand output |
|
The created documentation from the pull request is available at: docu-html |
PandaeDo
left a comment
There was a problem hiding this comment.
@FScholPer I appreciate the work so far. But I also think that we have to rework the report. For me it's unreadable. It would be great to have a overview and not so many details. The details should be available. But as a consumer of the informations you have to scroll to the complete document to find what you need. As we discussed this is also a POC. Fine for me for the moment. But if possible to spend some more time on improvement as described I would think that this report will find much more acceptance.
aschemmel-tech
left a comment
There was a problem hiding this comment.
see inline comments
| - For external component Assumptions of Use: coverage by platform safety manual or feature/components incl. test case, passed/failed and completeness verdict | ||
| - This is split in a list of QM requirements tested and a separate list of tests for ASIL rated requirements. | ||
| - List of component requirements (ASIL rated) linked to inspection checklist and verdict (derived from PR export) | ||
|
|
There was a problem hiding this comment.
Here it would be good to have overview pie charts like:
- req/aou inspected/valid/invalid
- req without testcases/with testcases linked
- req tested passed/skipped/failed
| **7. Test logs** | ||
| - Test log per test case with status passed/failed/not_run | ||
|
|
||
| .. needtable:: Test Logs Per Testcase |
There was a problem hiding this comment.
it is not clear for me what this table shows
links in the "need ID" do not work for me
Frank Scholter Peres frank.scholter_peres@mercedes-benz.com, Mercedes-Benz Tech Innovation GmbH
Provider Information