Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Right-click on a single finding or a group of selected findings and choose Suppress from the menu.

  2. Enter a reason for suppressing the finding and choose Choose where the suppressions will be stored. You can select one of the following options:

    • In source code - The selected finding will be suppressed in code and shared across the team when checked in your source control system.
    • Locally in file - The suppression will be stored in a parasoft.suppress file located in the same location as the corresponding source file. See In-file Suppressions for details.
    • On DTP- The suppression will be stored on DTP and shared with the team. You can only suppress findings that are already registered on DTP.

    Info
    iconfalse
    titleSuppressing Findings on DTP

    The On DTP option is only available for findings that have already been registered on DTP and are suppressed in the subsequent analysis run..

  3. Enter a reason for suppressing the finding.

    Info
    titleSuppressing false positives in MISRA compliance workflows

    If you implement a workflow for achieving compliance with the MISRA standard, you can exclude false positive violations from MISRA Compliance reports created on DTP. When you suppress a violation and specify a reason for suppression that begins with "false positive", the violation will not be included in MISRA Compliance reports. See the DTP User Guide for details about the Parasoft compliance solution

    Click OK to complete the suppression

    .

Anchor
In-file_Suppressions
In-file_Suppressions
In-file Suppressions

If you choose to store a suppression in a file, it will be stored in a parasoft.suppress file created in the same location as the source file that contains the finding. When you add a suppression, the file automatically opens in the IDE editor. The contents of the file may resemble the following:

Code Block
languagetext
suppression-begin
file: Simple.cpp
rule-id: SECURITY-22
message: Do not use mbstowcs() function
reason: verified
author: annstu
suppression-end

suppression-begin
file: Account.cpp
rule-id: JSF-043
message: Tabs should be avoided
reason: verified
author: annstu
suppression-end

See Defining Suppressions in Suppression Files for details about the suppression format and the complete list of available attributes.

...

  1. Enable the Show All Files option on the Visual Studio Solution Explorer toolbar or refresh the Solution Explorer if the option is already enabled. This will display files from outside the project, including the Parasoft suppression files.
  2. Right-click the suppression file(s) you add to your project and choose Include in Project from the menu.

If you use a source control system to track changes in source code, we recommend that you check in parasoft.suppress files to share your suppressions across the team.


Info
iconfalse
titleMigrating suppressions

Anchor
migrating_suppressions
migrating_suppressions
If your workspace contains suppressions that were created with older versions of C/C++test, you may be prompted to convert suppressions in the deprecated XML-style format into in-file suppressions. Conversion has the following consequences:

  • Suppressions in the deprecated format are converted into plain text and saved in parasoft.suppress files located in the same location as the corresponding source file.
  • A backup file that contains suppressions in the deprecated format is created. The location of the file is printed to the console.
  • Suppressions in the deprecated format are removed from the workspace.

Suppressions associated with files that are not available the workspace are not converted. The list of unconverted suppressions is printed on the console.

If you should want to restore deprecated suppressions from the backup file:

  1. Close your IDE.
  2. Go to the location where the backup file is stored (the location is printed to the console). It contains a 'cpptest' directory and a local_suppressions_backup.zip file.

  3. Remove the existing'cpptest' directory.

  4. Extract the contents of local_suppressions_backup.zip to the same location. A new 'cpptest' directory that contains restored suppressions will be created.

You can re-migrate restored suppressions on next IDE startup.

Reviewing Suppressions

You can review suppressed findings and unsuppress the findings that have been saved locally on desktop. 

...