Migration Test
Ensure that new tool versions don't introduce unintended changes in the behavior of your software.
Upgrading your toolchain is routine. Proving nothing changed silently is not.
In a model-based development process, the choice of tools and tool versions — for modeling, code generation, even the compiler — can affect the behavior of the software. Generated code often looks different after a code-generator upgrade, so how do you know the software still works the same way it did before? What you need is a migration test.
Back-to-Back Testing, run once per environment.
Migration testing applies the same Back-to-Back Testing mechanism used for software regression — but instead of comparing two versions of a model on one machine, it compares one model across two or more tool-version environments: the previous MATLAB/TargetLink or compiler configuration as reference, the upgraded configuration as comparison. BTC TestStack combines this with automated stimuli-vector generation for 100% completeness and 0% manual effort.
One workflow, distributed across your environments.
The testing effort itself can be automated with a script — but a complete migration test also means environmental challenges, like standing up containers or virtual machines with different tool versions side by side. This is where CI/CD tooling like Jenkins really shines.
Distribute environments
Jenkins agents each run a required software configuration — different MATLAB/TargetLink versions, different compilers, even a different operating system — so every environment under test is available in parallel.
Automated data transfer
The BTC TestStack plugin for Jenkins takes care of moving data between environments in the background. Point to the model files, and BTC TestStack and Jenkins take care of the rest.
Overview, then drill-down
A summary report shows the result across every environment at a glance, with the ability to drill into subsystem- or signal-level detail for any deviation found.
BTC TestStack
is ISO 26262 certified
The certificate addresses functional-safety standards across multiple industries:
For ISO 26262, BTC TestStack is certified with the highest Tool Confidence Level (TCL), valid for all ASIL levels including ASIL D. We provide the certificate and report to customers free of charge on request — removing most tool-qualification effort on the customer side.
Explore the rest of the stack.
Regression Test
Regression tests between different versions of a software play an important role in A-SPICE and ISO 26262.
Continuous Integration & Cloud
Include unit and integration tests in your CI pipeline to ensure high quality early on!
Back-to-Back Test
Back-to-back tests between model and code are highly recommended by the ISO 26262 standard.
Talk to our engineering team.
Tell us where your engineering problem actually is. We'll tell you whether an evaluation license, a workshop, or a conversation is the right next step.