In this section:

Configuring the Settings

C/C++test can be configured with settings (see Configuration Settings) that should be specified in a .properties file. The basic settings are listed in the cpptestcli.properties  file shipped in <INSTALL_DIR>.  By default, most settings are disabled. Uncomment the settings you want to enable and specify the parameters.Alternatively, you can store the settings in a .properties file in your home directory <USER_HOME_DIR> to ensure that the settings you configured are not affected by re-installation or updates. If a setting is configured in both the installation directory and the user's home directory, the value configured in <USER_HOME_DIR> overwrites the value in <INSTALL_DIR>.

 You can also create a custom .properties file and pass it to the cpptestcliwith the -settings switch.  You can use the -settings switch multiple times to specify several .properties files. Entries with the same key will be overwritten.

cpptestcli -settings team.properties -settings project.properties -settings user.properties -config "builtin://Recommended Rules" -compiler gcc_9-64 -input cpptest.bdf

Settings Hierarchy

General settings are applied in the following order: 

1. <INSTALL_DIR>/etc/cpptestcli.properties: the base configuration file that should not be modified.
2. <INSTALL_DIR>/cpptestcli.properties: the main configuration file you can use to specify your settings; it contains a list of basic configuration settings (license, reporting, etc.) you need to uncomment before configuring the setting's value.
3. <USER_HOME_DIR>/cpptestcli.properties: for your convenience, you can store the configuration file in your home directory to overwrite settings from the <INSTALL_DIR> (for example, to ensure your settings are not affected by re-installations or updates).
4. <WORKING_DIR>/cpptestcli.properties: for your convenience, you can store the configuration file in your working directory.
5. Custom settings passed with the command line switch -settings path/to/settings.properties (e.g., -settings ../settings.properties).
6. Custom settings passed with the command line switch -property [key=value](e.g. -property "report.mail.enabled=true").

All of the above settings can be overridden by settings that are passed with command line switches, such as -report, -config, etc.

Modifying a Single Property

You can quickly modify a single property in a settings configuration file with the -property switch  without creating a dedicated configuration:

cpptestcli -property dtp.url=https://dtp.parasoft.com.pl:8443 -config "builtin://Recommended Rules" -compiler gcc_9-64 -input cpptest.bdf

Viewing Current Settings 

Use the -showsettings option to print the current settings and customizations, including the origin file for each configuration. 

Auto-configuring Settings from DTP Server

You can specify settings in DTP and configure your Parasoft tool to use the settings when it connects to DTP Server. This enables you to use the same settings across multiple machines and configurations to ensure consistency. Edit the following setting in the .properties file to enable auto-configuration:  

dtp.autoconfig=true

Settings can be auto-configured for the entire organization or per project. 

Specifying Organization-wide Settings

1. Log into DTP with administrator credentials. 
2. Choose Report Center Settings from the settings menu.
   
3. Choose Global Tool Settings from the sidebar menu and enter the configuration settings from the.properties file in the space provided. Enter each setting on a new line. Use the # character to add comments.
   
4. Click Save.

Specifying Settings Per Project

1. Log into DTP with administrator credentials.
2. Choose Report Center Settings from the settings menu.
   
3. Click Projects in the Administration tab and click on a project. 
4. Enter the configuration settings from the .properties file in the Parasoft Tool Settings section. Enter each setting on a new line. Use the # character to add comments.
    
5. Click Save.

Advanced Configuration

For advanced configuration of C/C++test's native code analyzers, a dedicated configuration file (in a format supported by the analyzers) can be specified with -psrc <CONFIG_FILE> switch. Parasoft Support will provide content for the advanced configuration file.