NovaQTek
Home/Unit Test Automation
Unit Test Automation

Automated Unit Testing for Embedded C/C++

Generate, run, and maintain unit tests for safety-critical embedded software — with the structural coverage and traceable evidence that ISO 26262 and ASPICE demand.

Built for Standards-Driven Development

ISO 26262
Part 6 Unit Verification
ASPICE
SWE.4 Unit Verification
MISRA C
Coding Standard
AUTOSAR
Classic & Adaptive
IEC 61508
Industrial Safety
MC/DC
Structural Coverage

How It Works

From source code to audit-ready test evidence in four steps.

01

Analyze

Your C/C++ sources and headers are parsed to map functions, interfaces, and external dependencies.

02

Generate

Test cases, stubs, and harnesses are produced for each unit, ready to review and extend.

03

Execute

Tests run on the host or on target, on demand or as part of every pipeline build.

04

Report

Results and coverage are collected into reports that link back to code and requirements.

What You Get

Everything needed to take unit verification from a manual bottleneck to an automated part of the build.

Automated Test Generation

Unit test cases derived directly from your embedded C/C++ source, so engineers review tests instead of writing them by hand.

  • Function-level test cases
  • Boundary & equivalence values
  • Error and fault paths
  • Editable, readable test code
  • Regeneration as code changes

Stubs, Mocks & Harnesses

Hardware and software dependencies are isolated automatically so each unit can be tested on its own.

  • Stubs for external functions
  • Hardware register abstraction
  • AUTOSAR RTE & BSW interfaces
  • Test harness & build setup
  • Reusable across variants

Structural Coverage

Coverage is measured on every run and gaps are fed back into test generation until targets are met.

  • Statement coverage
  • Branch / decision coverage
  • MC/DC coverage
  • Coverage gap analysis
  • Targets per ASIL level

Host & Target Execution

Run the same tests on a development PC for fast feedback and on the target for final evidence.

  • Host-based (SIL) execution
  • Target & simulator execution
  • Cross-compiler support
  • Back-to-back comparison
  • Parallel test runs

CI/CD Integration

Unit tests become part of the build, so regressions are caught at the commit that introduced them.

  • Jenkins, GitLab CI, GitHub Actions
  • Automatic regression runs
  • Quality gates on coverage
  • Pull request feedback
  • Command-line & scripted use

Traceability & Reporting

Audit-ready evidence for safety assessments, generated with every test run rather than assembled afterwards.

  • Requirement-to-test traceability
  • Test specification & results
  • Coverage reports per unit
  • Evidence for ISO 26262 Part 6
  • Export for audits & reviews
Get In Touch

Contact Us

Ready to start your project? Reach out and one of our engineers will get back to you within 24 hours.

Walled Lake, Michigan, USA

View on Google Maps