You can run RVS automatically through the Jenkins continuous integration server. This lets you ensure that your verification results stay up-to-date throughout your project's entire life cycle.
After setting up an integration between RVS and Jenkins, a detailed RVS report is stored every time a build runs on the Jenkins CI server. The results are added to your project's history, letting you see the trend in your project's unit tests and the structural coverage and timing behavior of your code over time. If you've linked your unit tests to requirements, you can also track your requirements coverage over the course of your project.
Using these trends, you can easily identify which revision of your source code caused unit test failures, coverage holes or spikes in your software's worst-case execution time (WCET), so you can fix problems as they occur.
For more information, see our blog.
RVS also supports continuous verification with the Bamboo ALM tool.
Feature applies to: