In this release, we've focused on extending support for new compilers, as well as creating Compliance Packs that include new and enhanced test configurations:

Support for New Compilers

We've added support for the following compilers:

The compilers are now marked with the following support levels:

• Extended: Support has been validated with extended testing and is approved for use in safety-critical software development.
• Standard: Support has been validated with standard testing and is approved for use in non-safety critical software development.

See Compilers for details about currently supported compilers.

¹ C/C++test may not be able to analyze code that uses the latest versions of GNU GCC or Microsoft Visual C++ compilers with C++17 extensions enabled. The analysis results may also be inaccurate. C/C++test does not support the following C++17 extensions:

• P0017R1 Extension to aggregate initialization
• P0091R4 Template argument deduction for class templates
• P0127R2 Declaring non-type template parameters with auto
• P0195R2 Pack expansions in using-declarations
• P0522R0 Matching of template template-arguments excludes compatible templates

New and Updated Test Configurations

We've added the following built-in test configurations:

• AUTOSAR C++14 Coding Guidelines

• High Integrity C++

• SEI CERT C Guidelines
• UL 2900
• OWASP Top 10 2017
• DO178C Unit Testing
• ISO26262 Unit Testing
  

The rules enabled in the MISRA C 2012 built-in test configuration are now differently grouped and have new rule IDs, which may impact their previous suppressions; see MISRA C 2012 Rules for details.

Parasoft's Recommended FDA C++ Phase 1, 2, and 3 have been replace with the following test configurations:

• Recommended Rules for FDA (C)
• Recommended Rules for FDA (C++)

The "MISRA C" test configurations have been renamed as "MISRA C 1998".

The following test configurations have been removed:

• OWASP Top 10 Security Vulnerabilities (replaced with OWASP Top 10 2017)
• CERT C Coding Standard (replaced with SEI CERT C Guidelines)
• ISO 26262 Recommended Rules
• DISA-STIG Coding Standard
• SAMATE Annex A Source Code Weaknesses
• CRules

We've also updated the way the test configurations are organized. The built-in test configurations that enforce coding standards, such as MISRA, OWASP, JSF, and others, are now grouped in the aerospace, automotive, medical, and security compliance packs.

See Built-in Test Configurations for the list of test configurations shipped with C/C++test.

New and Updated Code Analysis Rules

In this release, we've added new static analysis rules to extend coverage of compliance standards; see New Rules and Updated Rules for the lists of new and updated rules.

MISRA C 2012 Rules

The rules that enforce the MISRA C 2012 Standard now have new rule IDs and are all grouped under one category "MISRA C 2012" to facilitate reviewing results and ensure full compatibility with Parasoft's MISRA C 2012 Compliance Pack.

• The layout and IDs of rules enabled in the MISRA C 2012 built-in test configuration have been updated; this may affect they way they are processed by DTP and their previous suppressions.
• The previous layout and IDs of MISRA C 2012 rules have been retained for backward compatibility as the "MISRA C 2012 (Legacy)" rule category –  custom test configurations that were created to enforce the MISRA C 2012 Standard with previous version of C/C++test automatically refer to this category and do not require updating.

The above changes do not impact rule implementations, which are identical for the "MISRA C 2012" and "MISRA C 2012 (Legacy)" rule categories.

Dynamic Stub Configuration with Stub Callbacks

The Stub Callbacks framework allows you to specify test case-specific stub behavior through the Test Case Editor interface or by manually modifying test case source code. You can define a specific stub logic that will be performed each time a stub is called during test case execution.

The Stubs API has been deprecated and is now disabled by default.

See Dynamic Stubs Configuration for details.

Enhanced Test Case Editor

We've enhanced the Test Case Editor to facilitate modifying test suites and test cases.

• The new "Stub Configuration" and "Stub Expectations" steps allow you to configure stub behavior using the Stub Callbacks framework (see Using Stub Callbacks for details).
• The "Additional Test Suite Code" editor enables you to configure code sections that are automatically added to your test suite code.

See Adding Test Suites and Test Cases with the Test Case Editor for details.

Reporting Test Execution Details

You can now generate an additional Test Execution Details Report that is linked to your regular report. The new report includes additional information about test execution – especially useful for teams developing safety critical applications. See Understanding Results.

Removed Support for Environments

IDEs

The following IDEs are no longer supported:

• Eclipse 3.5-3.7

Compilers

The following compilers are no longer supported (see Compilers for details about currently supported compilers):

Other Changes

• C/C++test Professional ships with C/C++test Standard (formerly DTP Engine for C/C++). The C/C++test Standard distribution is located in the C/C++test Professional installation directory. To use C/C++test Standard, unpack the distribution to a target location other than C/C++test Professional installation directory. See Parasoft C/C++test Standard for details.
• DTP 5.4.0 is required to leverage DTP capabilities and workflows.
• Findings marked with the Do Not Show priority on your DTP no longer simulate suppressions and should be converted to true suppressions; see DTP 5.4.0 Release Notes.
• The RuleWizard Module has been extended with the following nodes and properties:
  - the Explicit Template Instance node and its properties
  - the InitializerInClass property
  - the ReferenceQualifier property

Resolved Bugs and FRs

New Rules

The following rules have been added:

New rules have also been added to the following compliance categories:

Updated Rules