Analyze the code coverage achieved by software tests up to and including the MC/DC level.
Advanced MC/DC analysis.
Merge coverage from different builds automatically, such as system and unit tests.
RapiCover highlights missing MC/DC vectors to help you refine test cases.
Mark code as covered by manual analysis to justify not covering it during tests.
Justifications migrate when source code changes, automatically or after manual review.
A single store of justifications can be used by all users working on a project.
You can apply a single justification to multiple locations, reducing the effort involved in managing justifications in projects with many coverage holes of the same type.
Create and apply templates to add new justifications more easily.
Apply and use custom fields for your justifications.
Run tests on host computers and test rigs in continuous build environments.
Configure integrations of RVS into your development environment quickly and easily.
Take your test project from creation to completion with an intuitive user-interface.
After integrating one RVS tool to work a development environment, it is trivial to use others.
Multiple users can share the same test environment.
Apply analysis settings easily using a friendly user interface.
Identify tests that "hit" each tested element in your source code.
Remove selected coverage from reports to support continuous development.
Calculate the minimum set of tests to achieve identical coverage to a previous set of tests.
Compare reports from different builds to track project progress over time.
Export coverage results in a variety of formats.
View coverage and hierarchy of source code at a glance.
View source code with syntax highlighting and color-coding of results.
Easily filter results to focus your analysis.
Assign tests to datasets to support easy filtering of results.
Filter results by the test cases used to generate them.
Filter results by specific functions in source code.
Search reports for specific elements using advanced queries.
Collect data from almost any build system.
The recommended build integration strategy requires little if any change to the development environment.
Copy the build system to build and test code with RVS.
Collect data from almost any embedded target with flexible collection strategies.
Verify critical multicore systems.
Fit more tests on your target and reduce the number of builds you need to run.
Freeze and resume collection to eliminate incidental coverage from bootup programs.
Stream coverage data to collect it across target power cycles.
Collect verification data from LauterbachTM debuggers.
Collect verification data from iSYSTEMTM debuggers.
Test an almost unlimited number of conditions per decision and get more from the space on your target.
Run RVS automatically through Jenkins to collect and archive results.
Run RVS automatically through Bamboo to collect and archive results.
Support for C, Visual StudioTM, GCCTM, DiabTM and TASKINGTM compilers among others.
Support for C++, Visual StudioTM, GCCTM, DiabTM and TASKINGTM compilers among others.
Support for Ada 95, 2005 and 2012, GNAT ProTM and Green HillsTM compilers among others.
Support for mixed languages in the same code base.
Support for testing Assembly code.
Select floating or node-locked licenses with annual or perpetual duration.
Floating licenses support multiple users and shared working environments.
Node-locked licenses support use of RVS within a limited geographical area.
License RVS for use idefinitely.
License RVS in annual increments.
License usage data is exported in a format compatible for tracking using FlexNet Publisher.
Integration and learning resources help you get started verifying your code in no time.
Dedicated support service to resolve technical issues quickly.
Learn how to get the most from our verification solutions with simple, interactive tutorials.
Learn how to use RVS features with comprehensive documentation in both printed and electronic formats.
Qualification kits available for use in DO-178B/C projects.
Qualification kits available for use in ISO 26262 projects.
Additional evidence to qualify the use of RVS in your development environment.
We notify you of issues that may affect the validity of your results as soon as we identify them.