How to find untested high-risk code before a product release - Intro to Coco Code Coverage v. 7.5

Code coverage tells you how much you've tested. It doesn't tell you what matters. If you have 0% coverage on a simple 3-line function, that's probably fine. If you have 0% coverage on a function with 15 branches and nested loops, that's a bug waiting to ship. Coco 7.5 helps you tell the difference. CRAP metric — combines cyclomatic complexity with coverage into a single risk score. Functions that are both complex and untested score highest. You get a sorted list: start at the top, work down. No more deciding where to write tests next. cmimport — if your codebase is Python + C, you've been maintaining two separate coverage reports. cmimport merges them. One report, one place, one decision. Qt for MCUs — most embedded teams never get coverage on the actual device, because the setup is too painful. Coco now automates it: connect your board, run your app, get a full C ++ QML report. No debugger scripts. Coco Setup — a guided CLI that detects your compiler and generates scanner wrappers automatically. Coverage configuration used to require a specialist. Now it's a 5-minute task anyone on the team can do. Coco 7.5 is out now. Links below: Release notes & documentation: https://doc.qt.io/coco/release-notes.html Release blog: https://www.qt.io/quality-assurance/blog/release7.5.0.-coco-now-covers-python-ranks-testing-risk-with-crap-metrics-and-cuts-embedded-setup-overhead-qt-for-mcus Get to know Coco: https://www.qt.io/quality-assurance/coco 0:00 Why coverage percentages isn't enough to know 0:42 CRAP metric 2:15 cmimport to bridge multi-language gaps — Python + C unified 3:41 Coco Setup 5:01 Qt for MCUs coverage 6:08 Wrap-up #CodeCoverage #SoftwareTesting #QualityAssurance #EmbeddedDevelopment #QtforMCUs