In this section:

General

How can I get quick access to information about usage on the command line?

Use the -help command line switch:

cpptestcli.exe -help

How can I work with C/C++test via proxy?

Typically, if you connect through a proxy server, you need to configure the connection by passing protocol-specific system properties to the JVM – using the -D command line option.

To work with C/C++test, ensure that the system properties for the HTTPS protocol are configured. At a minimum, you must configure https.proxySet=true, https.proxyHost=[hostname], and https.proxyPort=[port number]. If your proxy server requires authentication, you can configure your credentials with the https.proxyUser and https.proxyPassword properties.

Your command line may resemble the following:

java -Dhttps.proxySet=true -Dhttps.proxyHost=myserver.example.com -Dhttps.proxyPort=8080 -Dhttps.proxyUser=user1 -Dhttps.proxyPassword=MyPassword

In addition, you can configure the https.nonProxyHosts property to specify hosts where connection via proxy is not required.

The proxy mode is not supported for Visual Studio.

If you use C/C++test on desktop with Eclipse, the proxy settings are automatically detected and do not need to be configured in the command line.

Installation

How do I fix a failed installation while integrating C/C++test with Visual Studio with a registry key suffix specified?

Providing a long registry suffix may lead to installation failure due to the path length limitation on Windows. To ensure that C/C++test is successfully installed, specify a shorter registry suffix during installation.

How can I prevent my machine ID from floating?

Changes in the network environment may affect the interface that is used to compute your machine ID and result in machine ID instability. You can use the PARASOFT_SUPPORT_NET_INTERFACES environment variable to specify a stable interface and prevent the machine ID from floating.

Set up the PARASOFT_SUPPORT_NET_INTERFACES environment variable.
Set the variable value to a stable Ethernet network interface. Do not use virtual, temporary or loopback interfaces.
- On Windows: Set the value to the MAC address of your network card. You can use the ipconfig -all command to obtain the address. For example:
SET PARASOFT_SUPPORT_NET_INTERFACES=00-10-D9-27-AC-85
- On Linux: Set the value to one of the network interfaces from the "inet" or "inet6" family. You can use the ifconfig command to obtain the list of available interfaces. For example:
export PARASOFT_SUPPORT_NET_INTERFACES=eth1

If the problem persists, you can obtain diagnostic information by setting up the environment variable PARASOFT_DEBUG_NET_INTERFACES and setting its value to true. This will print to the standard output the checking procedure that can be shared with technical support, as well as the interface that is used to compute your machine ID. The interface will be marked with the [SELECTED] prefix.

Testing and Analysis

What can I do if C/C++test reports a timeout during static analysis?

To ensure the analysis completes, you can do one of the following:

Increase the timeout limit by configuring the following option:
cpptest.analyzer.source.timeout=<TIMEOUT_IN_SECONDS>
See Configuring the Settings.
Disable the most time-consuming rules or metrics in your test configuration. The information about the times is included in the timeout message displayed on the console and in the report.
Contact Parasoft Support.

What if a file cannot be tested because its name is inconsistent between the source control and the testing input?

To correctly process and analyze a file, C/C++test must be able to match the file name you provided in the testing scope (i.e. the file name in your project) with the file name in the source control system. For this reason, if you are using a case-sensitive source control system, such a Git, you need to ensure that the file name capitalization is identical.

What if one or more files were not found when collecting static coverage data?

The setup problem that specifies the file (or files) that was not found when collecting static coverage data indicates that the local path of the file is different from its build-time path.

As a workaround, you can use the CPPTEST_COVERAGE_SRC_ROOT environment variable to map the original path to the local path:

CPPTEST_COVERAGE_SRC_ROOT=original/path1=local/path1;original/path2=local/path2;...

You can use '*' as an accepted wildcard in the original path. For example:

CPPTEST_COVERAGE_SRC_ROOT=/*/path=/local/path

You can also specify a list of path mappings in a list file (*.lst) and set its location as the value. For example:

CPPTEST_COVERAGE_SRC_ROOT=/path/mapping.lst

Each item in the *.lst file is treated as a separate entry.

Reports

What if some characters fail to be properly displayed in C/C++test reports?

Reports generated by Parasoft products require a sans-serif font to be available in your environment. If your report fails to correctly display some characters, such as national characters, ensure that a sans-serif font is installed on your system.

Working in the IDE

Why do I get notified that Parasoft Plugin or its components are slowing down Visual Studio 2017, 2019 or 2022 on startup?

In Visual Studio 2017, 2019, and 2022, performance management monitors and manages extensions that can affect startup time. As a result, a pop-up alert may appear when Parasoft Plugin is installed to indicate that Visual Studio startup time has increased. You can click the 'Manage performance' link in the pop-up window to review the startup times and disable displaying the alert.

Why are some Parasoft options not available in the Solution Explorer context menu in Visual Studio 2017?

To have access to all Parasoft options in the Solution Explorer context menu, ensure that one of the following workloads is installed with your Visual Studio 2017:

Desktop development with C++
Universal Windows Platform development or .NET desktop development

Run the Visual Studio Installer.
Select the appropriate workloads when prompted.

Why does Visual Studio 2015 not display code markers?

If the Parasoft DTP Plugin for Visual Studio is reinstalled, Visual Studio 2015 may fail to display code markers that indicate analysis findings or code coverage in the editor. This is caused by a Visual Studio known issue (see MEFCache bug breaks text adornments in any package for details).

To ensure that code markers are properly shown, clear the Visual Studio MEF cache each time you reinstall or updated the Parasoft DTP Plugin. Use one of the following options:

Use the Clear MEF Component Cache extension that will automatically clear the MEF cache (download here).
Manually delete the cache directory. Depending on your installation details, the cache directory may be available in the following locations:
- If the Plugin has been installed with the default options: %localappdata%\Microsoft\VisualStudio\14.0\ComponentModelCache
- If the Visual Studio registry suffix has been specified with the <SUFFIX> parameter during installation: %localappdata%\Microsoft\VisualStudio\14.0<suffix_name>\ComponentModelCache

Can I use Parasoft dotTEST and Parasoft C/C++test in the same Visual Studio IDE?

You can analyze code with Parasoft dotTEST and Parasoft C/C++test in the same Visual Studio if you install the Parasoft Plugin by running installers shipped with both products.

Go to the [INSTALL_DIR]/integration/vstudio directory of one product, run the Parasoft Plugin installer and follow the installation wizard. This will install the Parasof Plugin and enable the code analysis engine of the product.
Go to the [INSTALL_DIR]/integration/vstudio directory of the other product and run the Parasoft Plugin installer. The Parasoft Plugin is already installed, so the reinstallation/removal wizard will open. Select Reinstall and proceed with the wizard. This will enable the code analysis engine of the other product.

See Plugin for Visual Studio for details.