Explore Code Coverage with AI: Find Risky Code in Minutes

Most software teams measure code coverage but few use it to make decisions. 

A code coverage percentage tells you that tests ran. It doesn't tell you which functions are dangerously under-tested, which changes introduced unverified code, or where one new test would reduce the most risk before you deploy.

In this webinar, Qt Group Solutions Engineer, Marius Schmidt, with over 10 years in code coverage, testing, and quality assurance, shows teams building desktop applications, embedded systems, or connected devices how to move from gut-checking coverage to a ranked list of highest-risk functions, generated automatically from their own codebase on every sprint. Expect real code, live demos, and Q&A throughout.

Who Should Attend

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

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

What We Cover

• What code coverage actually means: Line, branch, and MC/DC coverage explained, where most tools stop short, and why that gap matters more than teams realize.

• 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 act on during sprint planning without debate.

• Why MC/DC changes what coverage means: Coco supports MC/DC, the condition-level standard required in safety-critical software. You'll see the difference live on a real codebase, and why branch coverage alone can miss risk entirely.

• AI-assisted test generation: How to feed your Coco reports into our AI assistant to generate the tests you're still missing and verify that the coverage metric actually improved.

• A live demo with real code: Every topic includes a live demo in Coco with a real codebase and time for Q&A.

You'll leave this session knowing how to get a first-ranked testing list.

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.

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.