From setup to results in minutes.
REQ-SAF-0042 · covered by 3 test case(s)
Developers own quality now — but the tools to prove it never moved into the IDE with them. Three gaps show up every day.
Every coverage check, traceability update and result review means leaving VS Code, wrestling a gcov/lcov/gcovr chain, and finding your place again. Testing becomes a separate chore instead of part of writing code.
Defects cost the least the moment you write them — yet feedback lands days later, in a QA cycle or a nightly build. As AI writes C/C++ faster than anyone can review it, that gap only widens.
gcov, lcov and gcovr give you coverage numbers, not qualification evidence for ISO 26262. Five open-source tools glued together is an unvalidated toolchain that stops at line and branch — no condition, no MC/DC.
Professional C/C++ testing that lives where you already work — with a qualified process behind every result.
One-click coverage and stubbing, live in-editor highlighting, and debugging — triggered from VS Code, no separate tool and no separate run.
Coverage and robustness results appear in the editor as you go, with zero build configuration to maintain. The same tests carry straight into CI.
Statement to MC/DC coverage, an automatically generated traceability matrix, and results written back to your requirements tool.
Six capabilities, one client, no context switch away from the editor.
Import and link requirements, then write test results back into VS Code. Connects to DOORS, Polarion, Jama, codeBeamer and SystemWeaver — a requirement change flows straight to the linked tests.
One-click statement, decision, condition, MC/DC, function, relational-operator and switch-case coverage, highlighted directly in the editor with per-line, per-test drill-down.
Missing functions and variables are stubbed automatically, and every stub can be customized to model the behavior a test needs.
Set breakpoints and step through code in VS Code with coverage insight visible alongside.
HTML reports covering test results, coverage figures and behavior plots, ready for a review or a safety case.
Plain C and C++, AUTOSAR Classic and Adaptive, with automatic generation of RTE or ara::com stub and harness code.
The model checking and coverage engines behind BTC TestStack are deterministic, whether the code under test was written by hand or suggested by an AI assistant. Built for GitHub Copilot, exposed to any agent through a BTC MCP server, and open to whichever model your team already runs.
Coverage appears in the editor as you write, instead of a manual gcov/lcov/gcovr run after the fact.
No build directory to maintain, no per-target scripting. Ready in minutes, not days.
Generated automatically as requirements are linked — not stitched together with custom scripts.
One qualified process behind every result, not five open-source tools glued together.
Every coverage metric BTC TestStack reports, including modified condition/decision coverage, is backed by a qualified tool process — not just a number.
The same TÜV SÜD certification also covers IEC 61508-3, ISO 25119, IEC 62304 and EN 50716 — provided free of charge with every license.
BTC TestStack supports GCC and MSVC toolchains across Windows and Linux.
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.
The same certified stack has other points of contact, and covers the use cases below.
Includes a two-hour onboarding workshop with our engineers, set up on your own C/C++ code, end to end.
