This topic explains how to review and customize project-level and file-level options, including build settings, custom compiler and linker options, Parasoft Project Center settings, and other settings.

Sections include:

Reviewing and Modifying Settings

The appropriate build settings must be configured in order for C++test to properly test your code. Additionally, Parasoft Project Center and Advanced Settings (instrumentation options) can be configured as needed.

To review and modify settings:

  1. Right-click the

     C/C++ Projects tree

     (a.k.a. "the project tree") node for the project or file whose settings you want to review and modify, then choose

    Properties from the shortcut menu. The Properties dialog will open.

  2. Expand the Parasoft> C++test category in the left pane.
  3. Select the category that represents the settings you want to review and/or change. Categories and available settings are described below.
  4. Modify the options in the right pane.
  5. Click Apply, then OK.

Available Settings

Build Settings

The available controls depend on the Options source selected.

Build system complexity and time required to perform a full project rebuild determine which options source is appropriate. 

If Use options from a build system is enabled:

  • C++test will automatically scan options from your build system
  • C++test will perform full rebuild of the project each time build options have to be rescanned

If Use options from a build data file is enabled: 

  • You must manually generate or update the build data file (e.g. during your regular build process).
  • You can can update the build data file while performing incremental builds.

If you decide to manually manage a build data file, integrating the mechanism for creating build data files into your build process is highly recommended. This is so that members of the development team can access and use your build data file, as well as helps you seamlessly generate or update it during regular build activities.

In C++test 7.1 and above, Use options from Makefile-based project was replaced by Use options from a build system.

To achieve the same functionality as that provided by Use options from Makefile-based project, use the following settings

  • Build command line: [ make -i -B CXX=${CPPTEST_SCAN} CC=$ CPPTEST_SCAN} LD=${CPPTEST_SCAN} clean all ]
  • Build working directory: [ ${project_loc} ]
  • Dependency file(s): [ ${project_loc}/Makefile ]

Managing Multiple C++test's Project Configurations

Multiple C++test Project Configurations can be used to manage tests for a range of different configurations. For example, you can configure a project for testing a host-compiler, cross-compiler, testing in Debug mode, testing in Release mode, etc.

You can also export current active properties to a file or import previously saved properties from a file:

  1. From right-click your project in the project explore and click Properties.
  2. Choose Parasoft> C++test and click Export or Import.
  3. Browse for the properties and click Save or Open.

Exporting a properties creates a file that's can also be used as an argument in the cpptestcli -localsettings parameter. This allows you to easily switch between different project configurations when testing from the command line.

Use options from a build data file

To configure the appropriate settings:

  1. In the Build data file field, enter or browse to the location of the build data file that was previously created (as described in Using cpptestscan or cpptesttrace to Create a Build Data File).
  2. If you want C++test to clear previous options information each time the options are scanned, clear the Keep previously collected options (incremental build) check box. Otherwise, each build will be treated as an incremental build.
  3. In the Compiler settings area, specify the compiler executable (for C and C++ sources), linker, and family.
  4. In the Options area, specify any test-specific C++test-specific options compiler or linker options that you want to use, and that are not already specified in the Makefile.

When the options in the specified build data file change, C++test will automatically rescan the options and modify the project accordingly. If you want to force C++test to update options immediately (for example, if an external configuration file has changed), click the Reset cache button. 

Use options from a build system

To configure the appropriate settings:

  1. In the Build command line field, review the options that C++test will use to run the build (e.g., execute make with the specified makefile) and collect project build options from that process.
  2. If your build system uses compiler/linker variables that are different than the default ones provided with C++test, modify the build command line as needed.

The build command line is preset to include the -B switch option (unconditionally make all targets). Only GNU Make 3.80+ supports this option. 

If you are using an earlier make, clean the build before creating a project. Keep the -k switch.

If you are using a make that does not support -B,  further modification of the command line is required. The default build command line used in the project properties does not have any targets. We recommend that you modify this command line with the target(s) used to build the code you want analyzed  For example:

make -i CXX=\${CPPTEST_SCAN} ... all (where all is a target).

Also, add a clean step prior to the normal build target. For example:

make -i CXX={CPPTEST_SCAN} ... clean all

This would first make the clean target, then all target. Although the make run from C++test will not actually build object files, the clean step will actually clean them.


       3. In the Build working directory field, specify the directory in which the build process should execute.

4. In the Dependency file(s) field, specify the Makefile(s) to be checked for changes. Options will be automatically updated if the specified file(s) changes.

5. In the Compiler settings area, specify the compiler executable (for C and C++ sources), linker, and family.

6. In the Options area, specify any test-specific C++test-specific options compiler or linker options that you want to use, and that are not already specified in the Makefile.

When the options in the specified dependency file(s) change, C++test will automatically rescan the options and modify the project accordingly. 

If you want to force C++test to update options immediately (for example, if an external configuration file has changed), click the Reset cache button. 

Use options from Microsoft Visual C++ 6.0 project

To configure the appropriate settings:

  1. In the Project file(.dsp) field, enter the location of the Microsoft Visual C++ (*.dsp) project file.
  2. In the Configuration field, select the configuration that you want to use.
  3. In the Build variables field, select the option that describes how you want C++test to configure $INCLUDE, $LIB and $PATH variables. Available options are:
  4. In the Compiler settings area, specify the compiler executable (for C and C++ sources), linker, and family.
  5. In the Options area, specify any test-specific/C++test-specific options compiler or linker options that you want to use, and that are not already specified in the Visual Studio 6 configuration.

When Visual C++ project file options change, C++test will automatically rescan the options and modify the project accordingly. If you want to force C++test to update options immediately (for example, if an external configuration file has changed), click the Reset cache button. 

Use options from Green Hills Software (GHS) project

To configure the appropriate settings:

  1. In the Root project file (.gpj) field, enter the location of the Green Hills (*.gpj) project file where you want to start options scanning.
  2. In the Project box, select a project, then click Refresh.
  3. In the Compiler settings area, specify the compiler executable (for C and C++ sources), linker, and family.
  4. In the Options area, specify any test-specific/C++test-specific options compiler or linker options that you want to use, and that are not already specified in the project.

When GHS project options change, C++test will automatically rescan the options. If you want to force C++test to update options immediately (for example, if an external configuration file has changed), click the Reset cache button. 


Additional Details on How C++test Uses a GHS Options Source

C++test supports following kinds of GPJ projects, meaning that it treats project nodes designated with these project types as projects to scan for sources and build options:

C++test divides GPJ projects into two groups:

The root project is the top-level project file selected as the one from which options scanning starts.

For projects of complex structure:

Testable sources are C and C++ sources.

There are two kinds of build options introduced by GPJ projects:

For C++test, build options (compilation options and build properties) for a specific source file include all options collected over all parent project nodes leading to this source, together with all options of the source node itself. Moreover, linking options for a specific testable project include all options collected  over all parent project nodes leading to this project, together with all options of the testable project node itself.

The following are recognized build properties, which may be specified from MULTI Build Options Editor:

For backwards compatibility with the GHS support available in previous C++test versions, the current version of C++test has a compatibility mode where the root project is always treated as testable, regardless of its type (as long as its type is supported). However, it may not be possible to build a test executable from a "not testable" project; two common reasons for this are:

The compatibility mode is primarily used for running static analysis on all the testable sources found in the complete project's hierarchy. 

Use options from Managed Make C/C++ project

To configure the appropriate settings:

  1. In the Configurations field, select the configuration that you want to use.
  2. In the Family field, select the compiler family that your compiler belongs to.
  3. In the Use custom commands area, specify any custom commands you want to use for the C compiler, C++ compiler, and/or linker.
  4. In the Options area, specify any test-specific/C++test-specific options compiler or linker options that you want to use, and that are not already specified in the project (e.g., as a Make-file target or in a Visual Studio 6 configuration).

Specify all options manually

To configure the appropriate settings:

  1. In the Compiler options field, enter the compiler options you want to use.
  2. In the Working Directory field, enter the directory where the compiler executes.
  3. In the Linker options field, enter the linker options you want to use.
  4. In the Compiler settings area, specify the compiler executable (for C and C++ sources), linker, and family. Compiler and linker settings should be consistent.

Execution (File-Level Only)

Determines whether the selected source file is instrumented during test case execution.

In order to apply this setting to multiple files, select files in the project tree, then right-click the selection and choose Parasoft> C++test> Execution Settings. Note that the current setting will be applied uniformly to all selected files.

Parasoft Project Center Attributes

Determines how results from this project or file are tagged for classification in Parasoft Project Center.

For details, see Connecting to Project Center.

Other Settings

Allows you to specify the location for C++test’s temporary files, as well as Advanced Options.

C++test Temporary Files 

The C++test temporary files field controls where C++test keeps temporary data/files, such as instrumented sources, compiled objects, linked test executables, and automatically-generated header files.  This setting controls {cpptest:testware_loc}.

Since C++test can automatically re-generate these files as needed, they do not need to be shared across team members. Thus, these files should not be saved within the project or added to source control. 

The temporary data can be deleted by clicking the Clear button. We recommend that you do not delete the temporary data between test runs; keeping this data can significantly improve performance.

For optimal performance, use a location on the local hard drive.

Advanced Options

This table allows you to specify various low-level and debug options; for a list of available options, see Advanced Instrumentation Configuration Options.

Source File Encoding

Determines if multibyte encoding should be used when processing source files. By default, C++test automatically activates support for multibyte characters based on the current system encoding (Auto mode). In order to manually control multibyte support, set the option value to On or Off.

Note that performance may be impacted by analyzing code with support for multibyte characters enabled.

Scope Settings

Allows you to specify project files that you do not want tested. See Testing a User-Defined Set of Resources for details.