https://blog.maxgio.me/tags/coverage/ Recent content in coverage on Maxgio's blog https://blog.maxgio.me/papermod-cover.png https://blog.maxgio.me/papermod-cover.png Hugo -- gohugo.io Sat, 22 Aug 2026 00:00:00 +0200 https://blog.maxgio.me/posts/the-binary-i-ship-is-the-binary-i-want-to-test/ Sat, 22 Aug 2026 00:00:00 +0200 https://blog.maxgio.me/posts/the-binary-i-ship-is-the-binary-i-want-to-test/ This article expands on my OpenSouthCode 2026 talk. I have a slightly awkward question for anyone who collects code coverage in CI: Are you testing the same binary that you ship? For many projects, the honest answer is no. Traditional coverage starts at compile time. Go builds need -cover. GCC uses --coverage, shorthand for -fprofile-arcs -ftest-coverage when compiling and -lgcov when linking. Clang’s LLVM source-based coverage uses -fprofile-instr-generate -fcoverage-mapping. llvm-profdata indexes the raw profile, and llvm-cov creates the report.