This page presents the evolution of the size of the system in lines of code (LoC).
The following metrics are visualized using a table showing the (absolute and relative) number of files as well as the LoC that are contained in rated intervals (The ratings: red=must be improved; yellow=should be improved; green=okay). The upper bound of the highest interval is the maximum values measured in the system. Furthermore, the evolution of the metrics is presented using stacked area charts (the areas in a specific color symbolize the number of LoC in the rating). At last for every metric a top 10 list of the files containing the most significant findings is presented. This table should be used as a starting point for a clean up of the code. Additionally, three links provide more detailed information about the metric: The Full Source Tree shows aggregations on different directory levels, the Tree Map visualizes the distribution in the system and the Sorted List presents the complete list of findings (in contrast to the top 10 list).
Please note: In the top 10 lists for "Nesting Depth" and "Longest Block" only the method with the worst metric value is mentioned. Thus, even if the file contains two or more methods that were on the top 10 range the file is only mentioned once with the most negative value measured.
Please note also: In the LoC-columns of the tables the sum of the LoC of all the files that contain at least one method with a red rating are added (not only the LoC of the red-rated methods). Furthermore, if a file contains at least one yellow-rated method all of its LoC are counted in the yellow interval. Only if a file contains only green-rated methods its complete LoC will be counted in the green interval.
This section presents the results of the clone detection which detects redundancies in the code caused by copy and paste programming.
This section presents a treemap that shows the distribution of clones within the system (generated code is marked using dashes). Furthermore, a download link is given that can be used to get the clone report that can be opened using the ConQAT client tools (Clone Detection Perspective). Below a table shows more detailed information:
| Column | Explanation |
| Element | This column presents the directories and the analyzed source files in a hierarchical way. |
| LoC | The lines of code contained in a file or directory. |
| Clone LoC | The lines of code in a file or directory that are covered by at least one clone. |
| Units | The number of statements contained in a file or directory. |
| Clone Units | The number of units in a file or directory that are covered by at least one clone. |
| RFSS | Redundancy Free Source Statements - The theoretical length of the file or directory if all clones would be removed. |
| UnitCoverage | The relative amount of clones compared to all units of a file or directory. |
| Clone Count | The number of clone classes contained in a file or directory. |
Findings represent different types of code defects, e.g. elements that are rated red concerning a metric, findings identified by external checking tools (PMD, FindBugs, FxCop ...) etc. The types of defects illustrated in this section should be extended in the future. The findings are presented using the following pages:
The "Task Tags" page presents all tags in the code that signalize that there is an open task. This analysis searches the code for comments that start with strings like "TODO", "FIXME" or "HACK". The results are shown in a treemap (to visualize the location in the system) and in a table.
Please notice that it is a good practice to mark open tasks in the code. This analysis should be used to track loose ends in the code. Please do not just remove the tags without solving the issue itself.
This documentation of the ConQAT-dashboard.
This section contains general informations about the execution of the ConQAT analyzes.
This page presents the log messages of the ConQAT execution. Usually no fatals and errors should be listed here if ConQAT was configures properly. Hint: You can sort the list by the severity of the log messages by clicking into the upper left corner of the table.
This page shows the config graph that has been executed by the ConQAT engine. At the bottom the parameters that have been passed to the block are presented. By clicking onto single blocks/processors the details on this element are shown.
Here the execution time of the individual blocks/processors in the configuration is visualized using a treemap.
The bundles used by the ConQAT installation can be seen on this page.