RapiCover Auto

Structural coverage analysis for automotive software

Where RapiCover Aero has benefited customers

RapiCover^Auto is specifically designed to meet the challenges of verifying automotive software written in C and C++ for critical embedded systems. The tool collects structural coverage measurements from software tests run on host computers, simulators or the embedded target itself.

By integrating seamlessly with your native build system, RapiCover^Auto lets you collect verification data automatically, for example in continuous build environments. Compared to similar tools on the market, RapiCover^Auto has extremely low overheads, so coverage data be collected in fewer test runs.

RapiCover^Auto meets the needs of ISO 26262 certification by collecting statement, branch and modified condition/decision coverage data, see the table below. The high-quality qualification kits available for RapiCover^Auto provide the evidence needed to qualify the tool for ISO 26262 projects.

Structural coverage metrics and ISO 26262 requirements

Measurement	Description	ISO 26262 requirements
Function coverage	Each function has been called at least once	At software architectural level, highly recommended at ASIL C & D Recommended at ASIL A & B (ISO 26262 part 6 10.4.6)
Call coverage	Each function has been called at least once, and each different function call has been encountered at least once	At software architectural level, highly recommended at ASIL C & D Recommended at ASIL A & B (ISO 26262 part 6 10.4.6)
Statement coverage	Each statement in the code has been encountered at least once	At software unit level, highly recommended at ASIL A & B Recommended at ASIL C & D (ISO 26262 part 6 9.4.5)
Branch coverage	Each branch in the code has been encountered at least once	At software unit level, highly recommended at ASIL B, C & D Recommended at ASIL A (ISO 26262 part 6 9.4.5)
Modified Condition/Decision Coverage	Decision coverage plus each condition has been shown to independently affect the outcome of its enclosing decision	At software unit level, highly recommended at ASIL D Recommended at ASIL A, B & C (ISO 26262 part 6 9.4.5)