https://notes.maxgio.me/tags/testing/Recent content in Testing on maxgio's notesHugo -- gohugo.ioen-usSat, 29 Aug 2026 19:52:33 +0200https://notes.maxgio.me/notes/the-binary-i-ship-is-the-binary-i-want-to-test/Sat, 29 Aug 2026 19:52:33 +0200https://notes.maxgio.me/notes/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.