Explore Code Coverage with AI: Find Risky Code in Minutes

The risk is already in your codebase. Your coverage report just isn't showing you where

Most teams optimise for the number... 85% of code coverage sounds healthy, doesn't it? The problem is that a percentage has no context: It can't tell you which functions are under-tested, which paths are critical, or where the next failure is most likely hiding.

In 40 minutes, you'll go from a coverage percentage to a ranked list of your highest-risk functions, generated automatically from your own codebase, ready to work down from the top before your next release.

About the session

Qt Group Solutions Engineer Marius Schmidt, with over 10 years in code coverage, testing, and quality assurance, shows teams how to stop gut-checking a percentage and start acting on an evidence-based list. Expect real code, live demos, and Q&A throughout.

What you'll learn

• Coverage that means something — line, branch, and MC/DC coverage explained, and why the gap between them matters more than most teams realise
• The CRAP score — a metric that combines cyclomatic complexity with coverage gaps to rank every function by risk. The result is a sorted list your team can work down from the top. No debate about where to start, no guessing about what to test next
• Why MC/DC changes everything — the condition-level standard required in safety-critical software, demonstrated live on a real codebase, showing exactly what branch coverage alone can miss
• AI-assisted test generation — how to feed your Coco reports into an AI assistant to generate the tests you're still missing, then watch the risk scores go down as the tests go in
• Live demo throughout — every topic includes real code in Coco, with time for Q&A

Instrument one component against your existing build and tests and get real CRAP scores on your own code the same day, whether that component runs on a desktop machine or a cross-compiled embedded target. Connect it to your CI/CD pipeline, and the ranked list will update automatically on every build.

The table above is built from real coverage data — explore it. Functions are sorted by CRAP score by default, with the riskiest at the top in red. Click any column header to re-sort. Try MC/DC and CRAP first

Who should attend

• QA leads and test managers who want to bring a ranked list to sprint planning, not a percentage
• Senior developers and embedded engineers who want an objective answer to where the next test should go, especially when hardware execution time makes every run count
• Engineering managers and CTOs who want release decisions backed by data, not instinct

If your team writes C, C++, C#, or QML for desktop, microcontroller, or connected device targets, this session is for you, whether or not you're already using Coco. The only prerequisite is recognising the gap between what your coverage report says and what your planning meetings actually need to hear.

Bring Your Team 

Bring the person who owns testing priorities and the person who owns your build pipeline or CI/CD configuration. Watching the session together means you can act on what you saw the same day, no handoff meeting required.

Can’t Make It Live?

Register anyway and we'll share the recording with you after the session.