Configuring Parasoft C++Test, dotTest and Jtest

A commonly used option for checking for Abstract Interpretation and Security violations are the Parasoft xTest tools.

Basic configuration

Configuring rule checkers in detail

For each one of these tools, a configuration file should exist in the TICS configuration directory:

• cpptest.properties
• dottest.properties
• jtest.properties

Configuring parameterization via the .properties file

Parameterization of a rule can be done as follows in the .properties file. For instance, this block will run the checker BD-API-BADPARAM with the options reportUnvalidatedViolations and aggressiveMode:

BD-API-BADPARAM=true
BD-API-BADPARAM-reportUnvalidatedViolations=true
BD-API-BADPARAM-aggressiveMode=true

Configuring parameterization via the IMPL.txt

The same can also be done via the TICS internal mechanism of the IMPL.txt file. To do parameterization in the IMPL.txt file, the following rules are used:

• a = separates the implementation ID from parameters
• a ; separates different parameters
• a : separates the parameter from its value

In practice, this looks like the following (for the same example as in the previous case):

BD-API-BADPARAM   CppTest   BD-API-BADPARAM=reportUnvalidatedViolations:true;aggressiveMode:true

Notes on the priorities of rule parameterization

• Rules will not be run unless they are in RULES/IMPL.txt, no matter what is in the .properties file.
• A rule can be disabled from running by removing it from RULES/IMPL.txt
• In the case that there is a conflict between the parameterization as given in the .properties file and the IMPL.txt, then priority will be given to the parameterization as used in the IMPL.txt file.

For more details on these, refer to the section on IMPL.txt.