This page will explain the Defects section in Code Analysis into detail.
Contents:
Every time the Kiuwan Code Analyzer detects a violation of any of the activated rules of the quality model, it generates a defect.
Kiuwan marks the exact location (file/line) in which these defects occur and, at the conclusion of the analysis, shows them in table form in the Defects page.
You can choose how Kiuwan shows the defects, grouped either by rule or by file. Where it shows:
Defects can be seen at rule, application, defect, and line of code level.
Each row of the defect table shows a defect and it associated violated rule.
The table can be filtered as follows:
Name | Description |
---|---|
Search by rule name | Search by the name of the rule |
Priority | The importance given to this rule in the Quality Model. |
Characteristic | One of the five Quality Model characteristics, which has been associated with the rule. |
Language | |
Normative | |
Framework | |
Tag | |
Muted | |
Status | |
Group by |
The content of the Defects table can be exported to an excel table, with the option in the header line where is located the "bread crumb".
The content of the Defects table can be sorted by any column, and the four columns on the right have the ability to "filter" the contents of the table.
Clicking on any of the fields of a table row, Kiuwan shows one row for each occurrence of the violation of this rule, indicating the row in the file where it is detected.
For each language, Kiuwan has three rules that detect similar —duplicate— code blocks:
The following screen shows an example of violation of these rules:
In xsl format.
This is a list in excel format, containing all violations found, with violated rule data and the file and line where it occurs.