Guides answer the questions engineers ask when they test Simulink models and C code: what a coverage metric means, what a safety standard asks for, what an error report tells you. Each guide is a list of questions with a short answer to each, followed by the detail and by how Reactis helps.
What modified condition/decision coverage is, how it differs from decision and condition coverage, a worked example, how many tests it needs, and how to measure and achieve it for Simulink models and C code.
The errors Reactis looks for in models and in C, how it finds them, what you get when it does, and what a clean result does and does not tell you.
Structural coverage, back-to-back testing, requirements-based testing, dead code, run-time errors and tool qualification under ISO 26262-6.
What DO-178C requires at each software level, how structural coverage relates to requirements-based testing, uncovered, dead and deactivated code, and model coverage under DO-331.