

To quickly analyze a Makefile-based project, ensure that the command line pattern includes the -trace option followed by the original build command, for example:Ĭpptestcli -trace make clean allĬommands that follow -trace are interpreted as a build command, so other C/C++test options must be listed first in the command line. Go to Extensions> C/C++test> Extension Settings> Command Line Pattern and adjust the command line for running C/C++test, depending on your build system. To analyze a project with C/C++test extension, you need to enable C/C++test Standard, which runs under the hood, to collect information about the original build commands. Importing Results from GitHub, GitLab and Azure DevOps.

Importing Results from a Local File or URL.Removing Violations from the Problems View.You can open the rule documentation to learn more about the problem. Review the results in the Problems view and the code editor.to run static analysis on the project you opened. See Supported Compilers for information about supported compilers. You must select the configuration that matches your compiler. See Built-in test configurations for information about available test configurations. By default, the Recommended Rules test configuration is configured.

and select a test configuration you want to use.Ī test configuration is a set of static analysis rules designed to cover an industry standard or best coding practices. and select the location where Parasoft C/C++test Standard is installed. The Quick Start menu offers easy access to the basic configuration options. Open the Command Palette and choose C/C++test: Quick Start or click C/C++test on the status bar at the bottom.To become familiar with the capabilities of the extension, you can use the ATM folder shipped with Parasoft C/C++test Standard in the examples directory. See Installing and licensing C/C++test Standard. Ensure that Parasoft C/C++test Standard is installed and licensed.
Visual studio code c trial#
