While RapiCover has very low instrumentation overheads, it may not be possible to collect all coverage from the same build or run due to code size or timing-related constraints.
If your software has code size constraints and it isn't possible to apply all instrumentation at once, you can configure your analysis to change the functions that are instrumented and merge results from multiple builds into the same report.
If your software has timing-related constraints, for example your code hits watchdog timers that halt execution during an instrumented build, when you run an RVS-instrumented build of your software, you can configure RVS to automatically remove instrumentation for coverage elements observed in a previous test run, allowing you to collect coverage incrementally across multiple test runs.
Feature applies to: