RKTracer Code Coverage Tool for 10 Programming Languages
- Very easy to use a Code Coverage tool with zero modifications to your application & very low memory overhead
- Supports Windows, Windows Drivers, Linux Desktop & Server, Linux kernel, and macOS
- Supports all Compilers, Cross-Compilers, and Embedded hardware with or without a file system, including Microcontrollers.
- Plugin for IDEs, i.e., Visual Studio IDEs, IAR Embedded Workbench, Keil Vision IDE, CCS Studio IDE, DS-5 ARM IDE, MPLAB IDE, Eclipse, etc.
- Easy to understand HTML Reports with detailed information.
- Supports CI Jenkins, Azure DevOps/PaaS, and SonarQube.
- Generates Code Coverage for Unit Testing, Integration Testing, or Functional Testing in User Space & Kernel Space.
- Quick 24/5 Support and Many more
RKTracer Tool Generated Code Coverage Reports
Do you need Code Coverage data?
Code Coverage metrics expose untested parts of code in dynamic testing, where testing can be unit testing or integration testing, or Functional testing of your application. Without code coverage reports, you will never know if all the lines of code/statements/conditions covered or uncovered. For that matter, without having code coverage metrics data, you might be writing redundant test cases. Coverage metrics will let you know how thoroughly you have tested your application and helps to improve the quality of testing.
Code Coverage is not only about line coverage, in a single line you can have multiple statements or conditions. Check for sample coverage reports above.
100% code coverage != quality testing, or quality of your product. However, code coverage reports help improve your testing process.
- Function Coverage
- Line Coverage
- Green Colour: covered code
- Yellow Colour: Partially covered code
- Red Colour: Not covered Code
- Statement Coverage
- Branch(Decision) Coverage
- Condition Coverage
- MC/DC Coverage Coverage
- Multiple Condition Coverage
How are code coverage metrics generated?
You need to rebuild your application by integrating the code coverage tool and test the application in the runtime environment. In the end, generate code coverage reports.
Code coverage tools can be divided into two types based on working principles.
- Source code level instrumentation: Tool will inject counters to source code and collects code execution data at runtime testing, and the process of adding counters is called instrumentation.
- Object code level instrumentation: Instrumentation takes place to vie to disassemble and collect coverage data at runtime testing.
How RKTracer Tool Works - 3 Simple Steps
The RKTracer tool can easily integrate with the existing build environment and generate code coverage reports with three simple steps.
Turn ON RKTracer or prefix rktracer to build command and rebuild the application.
Testing the instrumented application in the runtime environment
Generate Code Coverage Reports
Start Your Free 30 days Trial
- Round the clock technical support 24 hours a day, 5 days a week
- Trained support team to provide support during troubleshooting
- Advanced customer-specific build system documentation.