Ensure that new tool versions don’t introduce unintended changes in the behavior of your software!
In a Model-based development process, our choice in tools and tool versions for modeling, code generation, and even the compiler can impact the behavior of the software. This is why changing tool versions always comes with a risk, especially in larger projects.
Chances are high that, for example, the generated code looks different after you upgrade your code generator. So how can we know if the software still works in the same way as before? What we need is a migration test.
BTC EmbeddedTester manages this challenge automatically, by combining automated test generation with structural regression testing, ensuring 100% completeness with 0% manual effort.
Although the testing effort can easily be automated with a script, automating a complete migration test workflow also involves some environmental challenges, like setting up containers or virtual machines with the different versions of the tool.
This is a use case where tools like Jenkins really shine with their ability to distribute work to agents running the required software configuration. The workflow can even be automated for migration tests that involve switching to a new operating system!
The BTC EmbeddedPlatform plugin for Jenkins takes care of the required data transfer in the background. The user only needs to point to the model files, and BTC EmbeddedPlatform and Jenkins will take care of the rest. An overview report summarizes the results and lets you drill down into the details as needed.
To set up a migration test, all you need to do is specify the well-documented BTC EmbeddedPlatform test steps you’d like taken in your pipeline. The btc-embeddedplatform plugin (available in the Jenkins plugin manager) will take it from there.
Smart test generation for an ISO 26262 certified and fully automated Back-to-Back Test