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 | Required Action |
|---|---|---|
| Determine exactly what rules are checked during coding standard 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 |
| Modify static analysis settings, such as number of static analysis tasks reported per rule, 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 |
| Prevent the reporting of additional occurrences of a specific static analysis task | Suppress the task | |
| Create custom rules for checking application-specific, project-specific, and team-specific requirements | Use RuleWizard to create custom coding standards | Creating Custom Static Analysis Rules |
| Customize the built-in rules | Edit rule parameters in the Static tab of the Test Configurations dialog. or Use RuleWizard to modify static analysis rules | Creating Custom Static Analysis Rules |
Change rule categories, IDs, headers, and/or severities (e.g., to match your team’s or organization’s coding policy) | Define the changes with rule mappings | Modifying Rule Categories, IDs, Names, and Severity Levels |
| Create new rule categories | Define the changes with rule mappings | Modifying Rule Categories, IDs, Names, and Severity Levels |
| Change the default directory where SOAtest looks for user-defined rules | Set the desired User rules location in the Parasoft> Configurations page of the Preferences dialog. | Configuring SOAtest Across Teams |
