...
- Click the Change Search to open the search.
Configure your search criteria and click Search. The following search criteria are available:
Scroll Table Layout widths 30%,70% Filter
Build
A filter and build ID are the minimum criteria for searching violations. By default, the latest build selected when you change the filter, but you can choose a different build from the drop-down menu. The build selected functions as a target build when a baseline build is selected. See the following sections for additional information:
Baseline Build
State
A baseline build is any historical build used for comparison with another build. Choose a baseline build from the drop-down menu to search for violations reported from the baseline build to the build selected with the filter.
You can search for new, fixed, or existing violations by choosing a state from the State drop-down menu.
Severity You can search by one or more severity levels. Severity is determined by the test configuration. You can customize the severity level associated with a rule by creating a rule map. See Configuring Rules for additional information. Priority You can search by one or more assigned priorities. Priorities can be customized through the REST API. Author You can search by one or more code authors. Authorship is determined from the settings in the code analysis tool. Assignee You can search by one or more assignees. Action You can search by one or more assigned actions. Actions can be customized through the REST API. Type You can search for regular violations, suppressed violations, or all violations. Resource Groups A resource group is a collection of resources (i.e., files and/or folders) defined by a set of one or more Ant file patterns. You can search by one or more resource groups.
Resource groups can be defined in through the REST API.
Include File Pattern
Exclude File Pattern
You can specify Ant patterns to narrow or broaden the scope of your search. See Searching for Violations by File for details on configuring file patterns. Risk/Impact You can search by one or more risk/impact values. Risk/impact is the extent to which a violation impacts the business. Risk/impact can be customized through the REST API. Reference Number You can constrict your search to a specific reference number. Reference numbers can be added manually or automated through the REST API. Category You can search by one or more static analysis categories. Static analysis rules are organized into categories, but you can define or remap rules and categories by creating a rule map. See Configuring Rules for additional information. Module You can search by one or more specific modules. Limit You can set a limit for the number of violations shown in the Violations Explorer. - Click on a violation in the search results table to view the violation as it exists in the code.
...
You can search for a file and return the violations found in the file. The following table provides examples on how to set file paths.
| Scroll Table Layout | ||
|---|---|---|
|
| Value | Result |
|---|---|
| test | Returns all violations with file paths containing the string "Test", for example:
But not:
|
| com/ex | Returns all violations with file paths containing the string "com/ex", for example:
But not:
|
| com/parasoft/** | Returns all violations in the "com/parasoft" directory tree, for example:
But not:
|
| **/test/*.java | Returns all violations in files with the ".java" suffix under test directories from anywhere in the directory tree, for example:
But not:
|
...
Users must have permissions to prioritize violations, as well as view sources. Permission to prioritize violations can be granted for all violations or limited to violations owned by the user. The following table describes a project membership scenario and how permissions may be assigned (see Assigning Native Permissions for additional information):
| Excerpt | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...