Parasoft announces a new release of Parasoft C/C++test focusing on helping customers with the security of their C code, by bringing the most extensive Software Engineering Institute (SEI) CERT C solution to the market, with full static analysis coverage of the CERT C Security Coding Standard rules and dedicated compliance reporting. The new release also includes support for the AUTOSAR C++14 coding standard, a new approach to stubs configurations, enhanced unit testing reporting for compliance with safety standards, and support for over 20 new compilers and IDEs.
The growing number of firmware and IoT edge devices being developed in C have extended the chance of releasing code with security vulnerabilities more than ever before. Parasoft C/C++test’s new support for CERT C helps organizations detect security vulnerabilities in their code and manage the process of achieving compliance with the standard. This means the high accuracy of the code checkers, low level of false alarms, and sophisticated compliance reporting consistent with the CERT C standard, to help minimize related costs and overhead.
In addition to CERT C support, the new release of Parasoft C/C++test continues to focus on enabling customers to meet requirements imposed by functional safety and industry certification standards, with other new capabilities including:
• Support for the AUTOSAR C++14 and High Integrity C++ (HIC++) coding standards, enabling users from automotive and other industries to check the compliance of their C/C++ code.
• An enhanced stubbing framework that enables users to quickly build logic for stubbed code and easily share/re-use created assets for maximum flexibility. This framework adds to Parasoft C/C++test’s sophisticated unit testing solution that meets the requirements imposed by functional safety standards.
• Enhanced unit testing reports that document the unit tests execution results, including details about the test environment, test configuration, and executed test cases, that are typically required during code audits for compliance with standards such as IEC 61508, ISO 26262 and DO 178B, to prove that system requirements implementation is correct.