The code coverage tool for every language and target
RKTracer is a code coverage tool that measures every metric, from statement and branch to MC/DC, multi-condition and delta, without changing a single line of your source code. Run it on host machines, embedded targets, GPUs and simulators.
No source changes · works with every compiler · HTML and XML reports
# Just prefix your existing build command $ rktracer make all auto-detecting compiler: arm-none-eabi-gcc 12.2 instrumenting 142 source files… ✓ build complete, no source modified # Run your tests, then generate the report $ ctest && rkresults --report html ✓ statement 100% · decision 100% · MC/DC 99.2%
See exactly what your tests run, and what they miss
A code coverage tool measures how much of your source code your tests actually execute. It instruments the code, records which lines, branches and conditions run during testing, and reports the percentage covered, so you can find untested logic before it ships instead of after.
Most code coverage tools stop at statement or line coverage on a desktop build. RKTracer goes further: it measures the full set of structural metrics, up to MC/DC, on the real target you ship, and it does so without touching your source code or your build system. You prefix your build, run your tests however you already run them, and get an evidence-grade report.
Every coverage metric, from statement to MC/DC
One code coverage tool for the basics and for the hardest structural metric in software assurance.
Function, File & Line
Know exactly which functions, files and lines your tests execute.
Statement & Branch/Decision
Confirm every statement runs and both outcomes of each decision are tested.
Condition & MC/DC
The strongest structural metrics, the ones the highest assurance levels require.
Multi-Condition & Delta
Go beyond MC/DC, and focus coverage on exactly what changed each build.
Statement coverage is not enough for critical software
Safety standards do not just ask "did the line run?" They ask "was every condition independently shown to affect the outcome?" That is MC/DC, and it is the structural coverage the highest assurance levels call for. RKTracer measures it natively, alongside every other metric.
| Coverage metric | Called for at |
|---|---|
| Statement | DO-178C Level C · ISO 26262 ASIL A |
| Decision / Branch | DO-178C Level B · ASIL B/C |
| MC/DC | DO-178C Level A · ASIL D |
| Multi-Condition | Deep verification · IEC 61508 SIL 4 |
RKValidate is an ISO 9001 quality-certified vendor. RKTracer measures the coverage metrics these standards reference; it does not itself carry a functional-safety certification.
Color-coded to the line: green fully covered · amber partial · red uncovered.
Adopt the code coverage tool in an afternoon
No environment variables. No wrappers. No build-system surgery.
Prefix the build
Add the rktracer keyword to your build command. It auto-detects your compiler.
Instrument
RKTracer instruments during compilation, and adds its runtime automatically. Your source is never modified.
Run your tests
Run unit, integration, functional or UI tests on host, simulator, emulator or the real target. Coverage is captured live.
Get the report
rkresults emits HTML and XML for dashboards, CI and SonarQube. Merge reports across runs.
See the step-by-step guides for CMake, Makefile, IAR Embedded Workbench, Visual Studio and 30+ more toolchains.
One code coverage tool across your whole stack
Targets
- Host machines & servers
- Embedded targets (with/without FS)
- GPUs & CUDA
- Simulators & emulators
Languages
10 languages, one coverage model:
C/C++ standards: C89 through C17, C++98 through C++23, OpenMP and OpenACC.
Compilers & CI
- All compilers & cross-compilers
- IAR, Keil, Visual Studio, Eclipse, CCS
- Jenkins, Azure DevOps, GitLab
- Publishes to SonarQube
Coverage finds the gaps. Two ways to close them.
RKTracer pinpoints the uncovered lines, decisions and MC/DC conditions. Turning those gaps into tests is your choice, and both options are part of the RKTracer tool.
RKTracer itself measures coverage; it does not generate tests. The two tools below do.
Compare RKMCP and RKTracerGenRKMCP · AI-assisted
An MCP server that streams the uncovered code to your AI agent as JSON-RPC. The AI writes unit and functional tests plus the build, then runs and re-checks until the gaps close.
RKTracerGen · offline
A deterministic, fully offline unit-test generator. Boundary-Value Analysis, real-run oracle, managed stubs and a standalone Makefile. No AI, no tokens, no network.
Built for the work the others skip
| Capability | Typical code coverage tool | RKTracer |
|---|---|---|
| Setup | Wrappers, env vars, build edits | Prefix the build command |
| Source changes | Sometimes required | None |
| MC/DC & multi-condition | Often missing | Native |
| Embedded / GPU / simulator | Host-focused | All targets |
| CUDA coverage | No | Yes |
| Delta / changed-code coverage | Rare | Yes |
| Path to test generation | No | RKMCP (AI) or RKTracerGen (offline) |
| Reports & CI | Varies | HTML / XML, SonarQube, all major CI |
Code coverage tool questions, answered
rktracer, or enable the IDE plugin. No source edits, no environment variables, no wrappers. RKTracer instruments at compile time and adds its runtime automatically, even when cross-compiled.Run the code coverage tool on your own code
Download the free 30-day trial and run it on your target today, or book a 30-minute demo with an engineer.