In this section:
Table of Contents | ||
---|---|---|
|
Anchor | ||||
---|---|---|---|---|
|
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].
You can also create a custom .properties file and pass it to the cpptestcli
with the -settings
switch. You can use the -settings
switch multiple times to specify several .properties files. Entries with the same key will be overwritten.
Code Block |
---|
cpptestcli -settings team.properties -settings project.properties -settings user.properties -config "builtin://Recommended Rules" -compiler gcc_3_4 -input cpptest.bdf |
Info | ||
---|---|---|
| ||
Use double backslashes to specify file paths in the .properties file on Windows. For example:
|
Info | ||
---|---|---|
| ||
We highly recommend that you use encoded passwords to ensure successful authentication and increase the level of security; see Creating an Encoded Password. |
Settings Hierarchy
General settings are applied in the following order:
[INSTALL_DIR]/etc/cpptestcli.properties
: the base configuration file that should not be modified.[INSTALL_DIR]/cpptestcli.properties
: the main configuration file you can use to specify your settings that map contains templates for commonly used settings (license, reporting etc.).[USER_HOME]/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 reinstallations or updates).[WORKING_DIR]/cpptestcli.properties
: for your convenience, you can store the configuration file in your working directory.- Custom settings passed with the command line switch
-settings path/to/settings.properties
(e.g.,-settings ../settings.properties
). - Custom settings passed with the command line switch
-property [key=value]
.
All of the above settings can be overridden by custom settings that are passed with command line switches (e.g. -report
, -config
).
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:
Code Block |
---|
cpptestcli -property dtp.server=dtp.parasoft.com.pl -config "builtin://Recommended Rules" -compiler gcc_3_4 -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:
Code Block |
---|
dtp.autoconfig=true |
Settings can be auto-configured for the entire organization or per project.
Specifying Organization-wide Settings
- Log into DTP with administrator credentials
- Switch to Report Center and choose Report Center Settings from the menu.
- Go to Additional Settings> Report Center Administration.
- Choose Settings> Parasoft Test Global Settings and enter the settings from the
.properties
file. - Click Save.
Specifying Settings Per Project
- Log into DTP with administrator credentials
- Switch to Report Center and choose Report Center Settings from the menu.
- Choose Projects> Search and click Search.
- Click on your project name in the results and click the Parasoft Test Settings tab
- Enter the settings from the
.properties
and click Save.
Advanced Configuration
For advanced configuration of 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.