This site has limited support for your browser. We recommend switching to Edge, Chrome, Safari, or Firefox.

Cart 0

No more products available for purchase

Products
Pair with
Add order notes
Subtotal Free
Shipping, taxes, and discount codes are calculated at checkout

Your Cart is Empty

Safety-Standards Compliance for Google Test Suites

Migrating Existing Tests to QA-systems Cantata Hybrid 

Many embedded software teams rely on Google Test to validate functionality quickly and efficiently. However, when projects move into safety-critical domains such as automotive, aerospace, industrial automation, or medical devices, developer-focused testing alone is no longer sufficient.

Certification standards such as ISO 26262, DO-178C, and IEC 61508 demand deterministic execution, qualified coverage, full traceability, and auditable evidence.

QA-systems Cantata Hybrid enables teams to keep their existing Google Test suites while upgrading their verification process to certification-ready status without disruptive test rewrites.

Why Google Test Alone Is Not Enough

Google Test is an excellent framework for developer-level verification, but it was not designed to produce certification evidence. On its own, it does not provide qualified coverage measurement, controlled toolchain recording.

Cantata Hybrid closes this gap by adding qualified measurement, reporting, and execution control around existing tests while preserving the Google Test programming model.

A Build-Time Upgrade, Not a Test Rewrite

Cantata Hybrid integrates at the build-system level, typically through CMake. Instrumentation is applied during compilation and linking, ensuring that coverage and execution data are collected in a deterministic and auditable way.

A major advantage of Cantata Hybrid is that integration happens in CMake, not inside your test code. Below is a simplified version of the CMake additions shown in the highlighted screenshot, using Cantata Hybrid’s compiler launcher (cppccd) to instrument builds.

Example: Cantata Hybrid CMake Add-Ons

Key benefits include:

  • Preservation of existing Google Test investments
  • Auditable compiler and toolchain configurations
  • Qualified coverage data suitable for certification
  • Repeatable and defensible test execution

Designed for Embedded and Safety-Critical Systems

Many safety standards require testing on real target hardware or approved emulators. Cantata Hybrid supports cross-compiled embedded environments while maintaining deterministic execution and results.


From Developer Tests to Certification Evidence

Once integrated, Google Test suites become part of a structured verification workflow capable of producing assessor-ready artifacts:

  • Qualified coverage reports (statement, branch, MC/DC as required)
  • Deterministic, timestamped execution logs
  • Toolchain and configuration records for audit review

The Bottom Line

Achieving safety-standards compliance does not require abandoning Google Test. By introducing QA-systems Cantata Hybrid as a qualified instrumentation and reporting layer, teams can meet certification requirements while continuing to work with familiar tools.

The result is a faster path to compliance, reduced verification risk, and maximum return on existing test investments.

For more information, please contact us.