Why Coco is how it is | #SquishDays2021
This talk provides a high-level view on Coco for C and C++, describing how Coco works and why it is designed as it is. It explains why Coco must run as part of the compilation process and what it actually does when a compilation runs. This includes how Coco changes the source code during instrumentation, what is special about header files, and how the data about the code coverage are handled.
Oh, here is more
Webinar: The Cyber Resilience Act: What Waiting is Costing US Software Teams
Starting September 11, 2026, the EU Cyber Resilience Act (CRA) requires companies to report actively...
Watch VideoWebinar: Architecture-Guided Migration to Rust
Rust promises memory safety and modern tooling — but migrating a large, safety-critical C or C++ cod...
Watch VideoOn-Demand Webinar: CI/CD and Continuous Compliance of Embedded Software for Aerospace and Defense
Today, CI/CD for pure software products is well understood. But hardware dependencies and embedded d...
Watch VideoDe-Risking AI Playbooks: How to Build Visual UI Tests That Remain 100% Deterministic
Pixel-by-pixel UI testing is too brittle for modern release cycles, yet LLMs introduce a dangerous l...
Watch Video