About the RKTracer tool configuration file
The configuration system follows .gitignore conventions for simplicity. By default, RKTracer references rktracer.config in its installation folder. You can create custom project-specific configurations by copying this file to your project directory and renaming it with a .config extension (for example, project-name.config). Project-level configurations override installation-level defaults.
project-name.config
The original rktracer.config file in the RKTracer installation folder should never be deleted or modified, as it contains internal file exclusions from instrumentation by design.
Configuration use cases
The configuration file enables:
- Instrumenting selected files and generating coverage reports
- Instrumenting selected functions and generating coverage reports
- Enable mutation coverage generation
- Disable parallel build
- Generate XML reports
- Append or reset coverage data on update
- Generate MCDC code coverage
Next steps
For build-system examples that use the configuration file in practice, browse the rest of the documentation, or read more about how RKTracer measures coverage.