This topic explains how to configure C/C++test Professional.
Sections include:
If your organization is using Parasoft DTP, we strongly recommend that you adopt the following workflow to simplify configuration and updating of preference settings across your team:
To configure team-wide settings:
Choose Parasoft>Options in the IDE menu bar to open the Parasoft Preferences panel.
To configure each desktop and server installation to use the preferences stored on DTP:
Choose Parasoft>Options in the IDE menu bar to open the Parasoft Preferences panel.
The settings stored on DTP are automatically refreshed for your C/C++test istallation every time C/C++test is launched. To refresth the settins without restarting C/C++test:
If you’re working with multiple DTP projects, you can easily switch from one project’s settings to another by choosing a different project in the Configure Project dialog.
You can override team-wide preferences stored on DTP by configuring machine-specific preferences.
If you are using this recommended process, you can updated team-wide settings in Parasoft DTP, then those modifications will automatically be propagated to all the connected machines.
To prevent this automated updating (e.g., because you have updated settings locally and do not want them overridden), disable Use DTP settings on the Preferences page(s) you do not want to be updated from DTP.
To customize preferences:
Choose Parasoft>Options in the IDE menu bar to open the Parasoft Preferences panel.
Specifies general preference and allows you to export preferences to a localsettings file.Ignore solution and solution folder names in paths: Enables "reduced paths" mode. In this mode—where only reduced (project relative) paths are used. Names of solution and solution folders will be skipped in these paths. New paths will be unique because project names are unique inside a solution.
Maps a team member’s automatically-detected username to a different username and/or email address. See Configuring Task Assignment and Code Authorship Settings.
Specifies the number of Test Configurations available in the Parasoft> Test History menu, the location where custom static analysis rules (user rules) are saved and searched for, and the location where user-defined Test Configurations and rules are saved and searched for.
Specifies settings for the Console view.
Specifies setting for the DTP server. See Connecting to DTP.
When expanded, it allows you to configure settings for Team Server, which is deprecated (see Connecting to Team Server).
Specifies email settings used for report notifications and for sending files to Parasoft Technical Support. See Configuring Email Settings.
Determines the encoding for files without a BOM signature. You can choose to use the system defaults, indicate specific encoding, or automatically detect a specific Far-East language.
Specifies custom tags that the team uses to associate a test case with an issue from an issue/feature/defect tracking system (such as Jira). See Using Custom Defect/Issue Tracking Tags.
Specifies JDBC drivers (for example, drivers required to connect to a database used for parameterizing tests). See Configuring JDBC Drivers.
Specifies license settings. See Licensing.
Specifies parallel processing settings. See Configuring Parallel Processing.
Specifies general options related to how tasks are displayed in the Quality Tasks view. See Configuring Task Reporting Preferences.
Specifies what reports include and how they are formatted. See Configuring Reporting Settings.
Specifies how C/C++test computes code authorship and assigns tasks to different team members. See Configuring Task Assignment and Code Authorship Settings.
Specifies how C/C++test connects to your source control repositories. See Connecting Source Control.
Specifies options for preparing support archives and sending them to Parasoft Support. See Preparing a Support Archive.
The following variables can be used in reports, e-mail, Team Server, and license settings. Note that the session tag value can't contain any ':' characters.env_var
example: ${env_var:HOME}
Outputs the value of the environmental variable specified after the colon.
project_name
example: ${project_name}
Outputs the name of the tested project. If more than one project is provided as an input, it first outputs the tested project name, then "...".
solution_name
example: ${solution_name}
Outputs the name of the tested Visual Studio solution. If more than one solution is provided as an input, it first outputs the tested solution name, then "...".
general_project
example: ${general_project}
Outputs the name of the DTP general project that results are linked to.
workspace_name
example: ${workspace_name}
Outputs the workspace name or Visual Studio solution name. For example, report.mail.subject=Scanner Results for ${workspace_name}may evaluate to "Scanner Results for solutionAccoun1.sln".
solution_loc (Visual Studio)
example: ${solution_loc}
Outputs the Visual Studio solution location. For example, report.mail.subject=Scanner Results for ${solution_loc}may evaluate to "Scanner Results for c:/nightly/folder/.../solution.sln".
config_name
example: ${config_name}
Outputs the name of executed test configuration. Applies only to Reports and Email settings.
analysis_type
example: ${analysis_type}
Outputs a comma separated list of enabled analysis types. Applies only to Reports and Email settings.
tool_name
$ example: ${tool_name}
Outputs the name of the Parasoft product. For example:
Example:
You can export C/C++test preferences from the GUI to a localsettings text file. This is useful if you want to:
To export preferences to a localsettings file:
Choose Parasoft>Options in the IDE menu bar to open the Parasoft Preferences panel.
To preferences form a localsettings file:
Choose Parasoft>Options in the IDE menu bar to open the Parasoft Preferences panel.
By default, general Parasoft Preferences are common for all tested solutions/projects. To define preferences specific for a given solution:
Each time the solution is opened, the global preferences will be overridden by the ones read from the "parasoft.properties" file. After the solution is closed (or another solution is opened), global preferences will be restored.
Solution-specific preferences are read-only. If you modify any preferences in the GUI, the changes will not be reflected in the "parasoft.preferences" file automatically.
You can override the system user name, or example, if you are integrating the product into an automated process and do not want the resulting tasks assigned to the default system name.
<Install Directory>\plugins\com.parasoft.xtest.runtime.vstudio.core\parasoft.propertiesuser.name=<username>Note that this configuration is the equivalent to modifying the User name setting at the top level of the Preferences UI.
If you already have a locally-stored localsettings file that represents the settings you want to use for command-line execution, pass the location of the file using the -localsettings command line option, for example:
cpptestcli -localsettings my_localsettings_file |
See Configuring Localsettings and Testing from the Command Line Interface for details.
To configure your C/C++test instance to use settings stored on DTP, you can do one of the following:
Pass the name and port of DTP, as well as the project name, using the -dtp.autoconfig command line option, for example:
cpptestcli -dtp.autoconfig [email protected]:443 |
Enable the dtp.autoconfig option in a localsettings file, for example:
dtp.enabled=true dtp.server=mydtp dtp.port=443 dtp.project=project1 dtp.autoconfig=true |
See Configuring Localsettings for details.
To facilitate the testing process, you can specify different subsets of setting and pass them on the command line in a certain hierarchy. This allows you to simultaneously apply, for example:
Be sure to list the most general settings first and the most specific settings last. Settings are processed in the order in which they are listed and any settings that are duplicated across groups will be overridden each time a duplicate is found. Your command line may resemble the following:
cpptestcli -dtp.autoconfig [email protected]:443 -localsettings machine_properties -localsettings project_properties |