Features of collecting code coverage in the Neutrino OS

This article explores the technical aspects of collecting code coverage metrics for the Neutrino real-time operating system. The author notes that scaling this process to thousands of components and tests presents significant challenges beyond standard methods. The material details the lifecycle of coverage data, from generating .gcno and .gcda files during component builds to collecting trace files and aggregating them from various CI/CD pipelines. Special attention is given to the methodology of generating final reports and analyzing visualization tools. Specifically, the article discusses the limitations of the current lcov-based solution and justifies a strategic transition to gcovr to improve analysis efficiency. This article is useful for engineers involved in testing complex systems and automating software quality control processes in large-scale projects.
This is a summary. Read the full article at the original source:
HabrRelated stories
This Habr article explores fundamental data serialization issues that go beyond simple value equality. The author notes that the standard decode(encod…
In his latest post, Armin Ronacher explores the motivations behind the development of Astra, a new project focused on the coding experience. Ronacher…
We Replaced MMAP with Io_uring in Our Rust Query Engine. It Got Slower
The engineering team at Conviva recently documented an unexpected performance regression while optimizing their Rust-based query engine. Seeking to im…


