Parasoft C/C++test

Parasoft C/C++test is static analysis, unit testing and coverage software for C and C++ in safety-critical work, sold yearly with quote-only compliance plans.

Parasoft C/C++test catches defects and coding-standard violations early in C and C++ source, and produces the test and coverage evidence that functional safety audits ask for. Parasoft, a Monrovia, California testing company founded in 1987, develops it next to its Java and .NET tools, Jtest and dotTEST. It ships in two editions. C/C++test runs inside Eclipse, Visual Studio and VS Code. C/C++test CT works without an IDE and suits teams that test in CI pipelines with a unit testing framework of their own. Static analysis combines control flow, data flow and pattern-based checks, run in Fast, Standard or Aggressive mode. Data flow analysis flags null pointers, division by zero and memory leaks, while compliance checking covers MISRA, CERT, CWE, AUTOSAR C++14 and JSF, with OWASP rules for security. RuleWizard lets a team write its own rules, and code duplication analysis finds copied blocks. A reference report sets aside existing findings so newly introduced defects stand out. Unit and integration test generation, runtime analysis and coverage from statement and branch up to MC/DC run on host, simulator or target hardware, and requirements traceability ties each test to what it verifies. The audience is embedded software engineers, QA leads and safety managers in automotive, aerospace and defense, medical and industrial work. Those teams answer to ISO 26262, DO-178C or IEC 62304, and a TUV certificate with tool qualification kits covers qualifying the tool itself for ISO 26262 and DO-178C. A developer who simply wants bugs caught early can use the static analysis on its own. Teams that already write tests in GoogleTest or Boost.Test keep that framework under C/C++test CT and gain coverage, traceability and reporting on top of it. A typical project starts by running a MISRA or CERT configuration across the codebase, then turns the same rule set into a quality gate in Jenkins or Azure DevOps so every merge is checked. Developers get instant feedback in Visual Studio or VS Code while they work, and in VS Code a GenAI assistant suggests corrective code for each violation. Before an audit, coverage measured on target hardware and requirement links kept in Jama Connect or Polarion become part of the certification package. Managers then follow quality and compliance across projects in Parasoft DTP dashboards, which makes C/C++test a working part of how a safety-critical C or C++ team ships a release.