Updated rust coverage tools evaluation#2634
Updated rust coverage tools evaluation#2634alekseyborisyukvalidas wants to merge 2 commits intoeclipse-score:pawelrutkaq_symbol_report_covfrom
Conversation
alekseyborisyukvalidas
commented
Feb 27, 2026
alekseyborisyukvalidas
commented
- Update malfunction model
- Added qualification section
- Update malfunction model - Added qualification section
|
|
|
The created documentation from the pull request is available at: docu-html |
| - no | ||
| - high | ||
| - yes | ||
| - low |
There was a problem hiding this comment.
Can't this be elevated to high by providing a release test suite for reporting test cases based on edge case and fuzzy tests ? Why this then requires imidie qualification and not a mitigation technique and an additional judgment of likelihood based on scope of usage on codebases like libcore.
There was a problem hiding this comment.
This will be hard to argue. Mitigation usually is something that is done during every call of the tool, e.g. review of the output, inspection of the log etc.
Also, "test suite" is actually what "validation of software tool" qualification method of ISO suggest.
| - no | ||
| - high | ||
|
|
||
| .. [*] Expected that correctness of function calls are tested via mocking (e.g. gtest macro EXPECT_CALL()). |
There was a problem hiding this comment.
do not refer to cpp in rust
2 participants
