Static analysis can be highly customized. Use the following table as a reference to determine how to achieve the customization effect you are seeking:
| Desired Customization | Required Action | Reference |
|---|---|---|
| Define a set of rules to be used in static analysis | Change the rules settings in the Static tab of the Test Configuration(s) you want to apply | Static Tab Settings: Defining How Static Analysis is Performed |
| Customize available rules | Edit rule parameters in the Static> Rules Tree tab of the Test Configurations dialog. or Use RuleWizard to modify static code analysis rules | |
| Modify settings for BugDetective data flow analysis | Change the BugDetective settings in the Static tab of the Test Configuration(s) you want to apply | |
| Customize rule groups, identifiers, titles, and severities to match your policy and priorities | Define the changes with rule mappings | |
| Create new (fully-custom) static analysis rules | Use RuleWizard to create custom static code analysis rules | |
| Create new rule categories | Define the changes with rule mappings | |
| Change the default directory where C++test looks for user-defined rules | Set the desired User rules location in the Configurations page of the Preferences dialog. | C++test Configuration Overview |
| Apply local rule suppressions | Suppress the task | |
| Modify static analysis settings, such as number of tasks reported per rule, whether analysis is performed on automatically-generated test classes, etc. | Change the analysis settings in the Static tab of the Test Configuration(s) you want to apply | Static Tab Settings: Defining How Static Analysis is Performed |
In addition, you can configure static analysis with advanced options. For example, you can specify encoding or customize the amount of allocated memory. See Configuring Advanced Options for details.
