Table of Contents

Size

Metric	Key	Description
Accessors	accessors	Number of getter and setter methods used to get (reading) or set (writing) a class property. Getters Setters
Classes	classes	Number of classes (including nested classes, interfaces, enums and annotations).
Directories	directories	Number of directories.
Files	files	Number of files.
Generated Lines		Number of generated lines (Cobol seulement).
Generated lines of code		Number of generated lines of code (Cobol seulement).
Lines	lines	Number of physical lines (number of carriage returns).
Lines of code	ncloc	Number of physical lines that contain at least one character which is neither a whitespace or a tabulation or part of a comment.
Methods	functions	Number of methods. Number of paragraphs for Cobol. Notes for Java: Accessors are considered as methods if the sonar.squid analyse.property.accessors is set to false Constructors are considered as methods
Packages	packages	Number of packages.
Projects	projects	Number of projects in a view.
Public API	public_api	Number of public Classes + number of public Methods + number of public Properties (without public final static ones).
Statements	statements	TODO Java: Number of statements as defined in the Java Language Specification but without block definitions. Statements counter gets incremented by one each time a following keyword is encountered: if, else, while, do, for, switch, break, continue, return, throw, synchronized, catch, finally. Statements counter is not incremented by a class, method, field, annotation definition, package declaration and import declaration.

Tests

Metric	Key	Description
Branch coverage	branch_coverage	On each line of code containing some boolean expressions, the branch coverage simply answers the following question: 'Has each boolean expression been evaluated both to true and false?'. This is the density of possible branches in flow control structures that have been followed during unit tests execution.
Coverage	coverage	It is a mix of Line coverage and Branch coverage. Its goal is to provide an even more accurate answer to the following question: 'How much of the source code has been covered by the unit tests?".
Line coverage	line_coverage	On a given line of code, Line coverage simply answers the following question: 'Has this line of code been executed during the execution of the unit tests?'. It is the density of covered lines by unit tests:
Lines to cover	lines_to_cover	Number of lines of code which could be covered by unit tests (for example, blank lines or full comments lines are not considered as lines to cover).
New branch coverage	new_branch_coverage	Identical to Branch coverage but restricted to new / updated source code.
New coverage	new_coverage	Identical to Coverage but restricted to new / updated source code.
New line coverage	new_line_coverage	Identical to Line coverage but restricted to new / updated source code.
New lines to cover	new_lines_to_cover	Identical to Lines to cover but restricted to new / updated source code.
New uncovered lines	new_uncovered_lines	Identical to Uncovered lines but restricted to new / updated source code.
Skipped unit tests	skipped_tests	Number of skipped unit tests.
Uncovered branches	uncovered_branches	Number of branches which are not covered by unit tests.
Uncovered lines	uncovered_lines	Number of lines of code which are not covered by unit tests.
Unit tests	tests	Number of unit tests.
Unit tests duration	test_execution_time	Time required to execute all the unit tests.
Unit test errors	test_errors	Number of unit tests that have failed.
Unit test failures	test_failures	Number of unit tests that have failed with an unexpected exception.
Unit test success density (%)	test_success_density	Test success density = (tests - (test_errors + test_failures)) / tests * 100

The same kinds of metrics exist for Integration tests coverage and Overall tests coverage (Units tests + Integration tests).

Metrics on tests execution does not exist for Integration tests and Overall tests.