BTC TestStack · for VS Code

Safety-grade C/C++ testing — native in your IDE.

From setup to results in minutes.

Request an evaluation license

⌕ motor_control

Visual Studio Code

214static bool handle_overcurrent(void)

215{

216if (current_mA > MOTOR_MAX_CURRENT_MA)

217{

219fault_status.overcurrent = true;

220motor_set_state(MOTOR_STATE_FAULT);

221log_event(EVENT_OVERCURRENT_FAULT);

223return true;

224}

225return false;

BTC TestStack

Coverage summary

98%MC/DC

98%Branch

98%Statement

Test cases · 12/12 passed

✓ TC_MOTOR_001 · Overcurrent detection✓ TC_MOTOR_002 · Speed command validation

Traceability

REQ-SAF-0042Covered by 3 test cases

GCC & MSVC · Windows & LinuxPowered by BTC QCore

The challenge

Professional testing shouldn't mean leaving your editor.

Developers own quality now — but the tools to prove it never moved into the IDE with them. Three gaps show up every day.

Testing lives in a different tool than the code

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.

Feedback arrives too late to be cheap

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.

Numbers aren't a safety case

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.

The solution

Native, qualified, ready in minutes.

Professional C/C++ testing that lives where you already work — with a qualified process behind every result.

In the editor

Everything runs inside the editor

One-click coverage and stubbing, live in-editor highlighting, and debugging — triggered from VS Code, no separate tool and no separate run.

Immediate feedback

Feedback the moment you write the code

Coverage and robustness results appear in the editor as you go, with zero build configuration to maintain. The same tests carry straight into CI.

Qualified process

A qualified process behind every result

Statement to MC/DC coverage, an automatically generated traceability matrix, and results written back to your requirements tool.

Key capabilities

Everything a unit/integration-level test needs, in one place.

Six capabilities, one client, no context switch away from the editor.

Requirement ↔ test traceabilitySource: Polarion

REQ_SHC-76 · CondCheckOK

└─✓Test_CheckConditions_ReturnsTrue

REQ_SHC-77 · Stage 2PENDING

└─?Test_CyclesThroughAllStagesImpacted by change

REQ_SHC-78 · Stage 3OK

└─✓Test_StageThreeTransition

Requirements01

Requirements-based testing

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.

Test explorer

✓ Test_CheckConditions_ReturnsTrue✓ Test_CheckConditions_ReturnsFalse× Test_Controller_CyclesThroughAllStages

Statement72%

Decision61%

MC/DC48%

65heatingCoil = high;

66leds[0] = 1;

67leds[1] = 1;

68leds[2] = 1;

70} else if (state.temperatureStage == 2) {

76}

Coverage02

Code-coverage analysis

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.

Interfaces · seat_heating_controller● Apply auto-stub

SymbolCategoryStub mode

TemperatureParamsGlobal variable—

stateStatic variable—

check_conditions(…)Sub-functionReal, no check

request_power(…)Sub-functionReal, no check

bool getButtonPressed()External functionLink stub

Stubbing03

Stubbing & mocking

Missing functions and variables are stubbed automatically, and every stub can be customized to model the behavior a test needs.

motor_control.cpp

214static void handle_overcurrent(void)

215{

216if (current_mA > MOTOR_MAX_CURRENT_MA)

217{

219fault_status.overcurrent = true;

220motor_set_state(MOTOR_STATE_FAULT);

224}

Now covered by this debug run

Call stack

handle_overcurrent()motor_control_step()main()

Variables

current_mA 185MOTOR_MAX_CURRENT_MA 150fault_status.overcurrent true

Step overContinue

Debugging04

Debugging

Set breakpoints and step through code in VS Code with coverage insight visible alongside.

Test resultsRequirements 2Code analysis 74%

Test results

8/12 passed · 66.6%

Coverage

74%

Test nameRequirementResult

Test_CheckConditions_ReturnsTrueREQ_SHC-76Passed

Test_CyclesThroughAllStagesREQ_SHC-77Failed

Reporting05

Test reporting

HTML reports covering test results, coverage figures and behavior plots, ready for a review or a safety case.

AUTOSAR ClassicSeatHeatingComponentSender-Receiver · Classic Platform

SeatTemp_degCHeaterDuty_pctSetOccupied : boolTargetStage : uint8

AUTOSAR AdaptiveSeatHeatingAppService-oriented · Adaptive Platform

DiagnosticServiceSeatHeatingServiceStatusChanged : eventCurrentLevel : field

Architectures06

Test architectures & languages

Plain C and C++, AUTOSAR Classic and Adaptive, with automatic generation of RTE or ara::com stub and harness code.

AI & agentic workflows

AI writes the code. BTC TestStack proves it works.

Deterministic by design

Code generation and verification stay two distinct disciplines.

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.

generate_stub() → done

coverage_analyze() → 92% MC/DC

verify_proof_property() → proven

Key benefits

What changes on day one.

Live, one-click coverage

Coverage appears in the editor as you write, instead of a manual gcov/lcov/gcovr run after the fact.

No setup tax

No build directory to maintain, no per-target scripting. Ready in minutes, not days.

Integrated traceability matrix

Generated automatically as requirements are linked — not stitched together with custom scripts.

A qualified process, not a patchwork

One qualified process behind every result, not five open-source tools glued together.

Proof

Qualified, certified, provided free of charge.

Qualified up to MC/DC

Every coverage metric BTC TestStack reports, including modified condition/decision coverage, is backed by a qualified tool process — not just a number.

TÜV SÜD · ISO 26262, certified up to ASIL D

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.

GCC and MSVC, on Windows and Linux

BTC TestStack supports GCC and MSVC toolchains across Windows and Linux.

Certified

BTC TestStack

is ISO 26262 certified

The certificate addresses functional-safety standards across multiple industries:

ISO 26262

Automotive

IEC 61508-3:2010

Industrial / cross-industry functional safety

ISO 25119

Agricultural & forestry machinery

IEC 62304

Medical device software

EN 50716

Railway / rail applications

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.

Keep exploring

One stack, more ways in.

The same certified stack has other points of contact, and covers the use cases below.

Model-based

BTC TestStack × Simulink

Test the model and the generated code in one workflow, native in Simulink.

Scale out

BTC TestStack × Cloud

Run test and verification workloads at the scale of your pipeline, in the browser.

Key use casesCode Coverage Analysis Requirements-based Testing Formal Verification

Feel the Quality

Request an evaluation license.

Includes a two-hour onboarding workshop with our engineers, set up on your own C/C++ code, end to end.

Request an evaluation license Book a Demo