You can now add C or C++ "support" functions to your RapiTest tests. These functions let you create test logic that is reusable across multiple tests so you can perform functions such as initialization or teardown, defining complex sets of checks, implementing complex stubs, and instantiating templates.
You can generate and verify your support functions in the RVS Project Manager and use them in any of RapiTest’s test formats.
RapiCover now helps you to collect your coverage incrementally if you need multiple builds to collect coverage due to the timing overheads of instrumentation.
By enabling incremental coverage, you can now instruct RapiCover to automatically remove instrumentation for code elements that have already been collected. Combined with RapiCover’s already low overheads, incremental coverage helps you work around execution time limitations on embedded targets and build your way to 100% coverage more efficiently than ever.
You can now test your object code without modifying it with RapiTest. By separating test harness code from original object code and linking the two together to create the final executable, RapiTest lets you test your original compiled object code.
This capability can be set up during a RapiTest integration.
RapiTimeZero now supports merging timing results from multiple test runs, allowing you to collate timing results collected from them into a final report. This feature even lets you merge results from different testing strategies, e.g. system testing and low-level testing, so long as the functions under test are identical.
RVS: Setting the standard for safety-critical software verification
"We use the tool on some of the world’s most complicated flight control systems. Compared to previous tools we’ve used in the past, RapiCover’s performance has been much more reliable and robust" - Collins Aerospace Flight Controls