Regression Test
Confirm nothing changed — after any model, code, or tool-version update.
An upgraded toolchain or a restructured model can change behavior — silently.
When teams upgrade their code-generation toolchain, or restructure a model or its production code, there's no reliable way to confirm behavior hasn't shifted — short of re-testing everything by hand.
Back-to-Back Testing, applied to two versions.
Regression testing applies the same Back-to-Back Testing mechanism to two versions of the same implementation, instead of two different implementations — the previous version as reference, the current version as comparison. The same stimuli vectors, the same two engines, and the same report types apply.
Software regression, or tool qualification.
Software regression
Especially important for changes like code optimization or restructuring, where behavior should stay identical — a regression test proves it did.
Tool qualification
When teams upgrade their code-generation toolchain, this comparison provides formal evidence that the generated code has not changed behavior — replacing manual re-review with automated, traceable comparison.
Stimuli vectors, run on both versions.
Stimuli vectors are generated automatically to reach structural and robustness coverage goals — using a fast heuristic engine (ATG) and a formal, model-checking engine (CV) that can mathematically prove a goal is unreachable. The same vectors run against both versions; any deviation is flagged and localized automatically.
See the full Back-to-Back Testing mechanismHandles large models and busy pipelines.
Hierarchical test approach
For large models, regression testing becomes a challenge when you only focus on the top level. BTC TestStack can analyze child scopes independently before aggregating to the top-level scope, keeping generation tractable as complexity grows.
More on the hierarchical approachTest automation & CI/CD
The test automation add-on runs regression workflows unattended — triggered by a script or Jenkins, with a comprehensive HTML report on completion, a REST API, and a Linux-based container image for your own servers or the cloud.
More on CI/CD integrationEvidence built for the qualification package.
Every regression run produces the same Back-to-Back Test Report, Code Analysis Report, and Model Coverage Report used across BTC TestStack — versioned as profile items and exportable for tool qualification packages or customer documentation.
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.
Back-to-Back Test
Back-to-back tests between model and code are highly recommended by the ISO 26262 standard.
Migration Test
Ensure that new tool versions don't introduce unintended changes in the behavior of your software!
Continuous Integration & Cloud
Include unit and integration tests in your CI pipeline to ensure high quality early on!
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.