Coco is now certified by German TÜV as suitable for verification of safety-related software up to the highest integrity levels of ISO 26262 (ASIL D), IEC 61508 (SIL 4), IEC 62304 (Class C), and EN 50716 (SIL 4), giving safety-critical teams a certified coverage tool, a ready path to qualifying it, and the evidence audits require.
For teams building safety-critical software, reaching a functional safety standard is demanding and time-consuming. Every tool in the development chain has to be qualified for its intended use; the right coverage evidence has to be produced to the level the standard requires, and all of it has to hold up under audit. Tool qualification alone is often one of the slowest steps on the path to certification.
Qt Group is addressing part of that challenge for code coverage. Coco, its code coverage analysis tool, has now been independently certified by a TÜV body as suitable for verifying safety-related software up to the highest integrity level defined in four cross-industry functional safety standards:
For teams, that brings the pieces of audit-ready coverage together in one place: a certified tool, a ready path to qualifying it for their own project through the Tool Qualification Kit for Coco, and the coverage evidence auditors expect.
Coverage evidence for the highest safety levels
For the highest safety levels, standards call for Modified Condition/Decision Coverage (MC/DC), which many free and open-source tools do not provide. Coco produces per-file, per-function, per-branch, and MC/DC reports that trace back to the specific test cases that generated them.
Nico Kaufmann, R&D Manager, Software Quality Solutions, at Qt Group, said: 'Getting code coverage audit-ready across automotive, industrial, medical, and railway has usually meant different tools and separate qualification efforts. Coco is now certified as suitable up to the highest level in all four, and its Tool Qualification Kit gives teams a ready path to bring it into their own projects.'"
Availability
Coco is available now. To see how Coco fits your next certifiable project, visit qt.io/quality-assurance/coco or contact the Qt Group Software Quality team: qt.io/quality-assurance/contact-us.
Quick facts
● Product: Coco (code coverage analysis tool from Qt Group)
● Certifying body: SGS-TÜV Saar
● Certification: Coco is suitable for verification of safety-related software up to ASIL D (ISO 26262), SIL 4 (IEC 61508, class T2 tool), software safety Class C (IEC 62304), and SIL 4 (EN 50716, class T2 tool).
● Certified languages: C and C++
● Also supported (outside the qualification scope): C#, Python, QML, and Tcl
● Coverage metrics: statement, branch/decision, condition (MC/DC), function
● Tool qualification: a Tool Qualification Kit helps teams qualify Coco for their own project
● Embedded: coverage on common microcontroller targets and cross-compilers used in safety-critical development
Frequently Asked Questions
Which safety standards is Coco certified for?
Coco is certified as suitable verifying for ISO 26262 (automotive, up to ASIL D), IEC 61508 (industrial, up to SIL 4), IEC 62304 (medical, up to Class C), and EN 50716 (railway, up to SIL 4).
Can Coco be used for projects for ISO 26262 ASIL D projects?
Yes. Coco is TÜV-certified as suitable for ISO 26262 up to ASIL D.
Does the certification mean we no longer need to qualify Coco ourselves?
No. You still qualify Coco for your own project and environment; the certification gives independent confidence in the tool itself. Coco's Tool Qualification Kit supports that step. Confirm exact acceptance of conditions with your certification authority.
Which languages does Coco support?
The certification covers C and C++. Coco also supports C#, Python, QML, and Tcl, which are part of the product but outside the scope of this TÜV certification.
Does Coco support MC/DC coverage?
Yes. Coco measures Modified Condition/Decision Coverage (MC/DC), the coverage metric required for the highest safety integrity levels.
Can Coco be used on embedded targets?
Yes. Coco collects coverage directly from resource-constrained embedded targets, including microcontrollers from NXP, Infineon, Renesas, STM32, Microchip, and TI AURIX, with common cross-compilers such as ARM GCC, IAR, Green Hills, HighTec, Clang, and Diab, and environments from bare-metal to FreeRTOS, QNX, VxWorks, Zephyr, and SafeRTOS.
Subscribe to our blog
