Check = Coding Rule.
A good coding practice. Not complying to coding rules leads to quality flaws and creation of issues in SonarQube.
Coding rules can check quality on files, unit tests or packages.
|See Viewing Unit Tests > Issues TabPerspective|
|A piece of software (project, module/package, file) or a view or a developer.|
A property of a component. Examples: number of lines of code, complexity, etc.
A metric may be either:
The value of the metric for a given component is called measure.
|See detailed documentation on metrics.|
The value of a metric for a given component at a given time.
A set of coding rules.
Each snapshot is based on a single quality profile.
|See Quality Profiles.|
A set of measures and issues on a given component at a given time.
A snapshot is generated for each analysis.
When a component does not comply with a coding rule, an issue is logged (was violation prior to SonarQube 3.6) on the snapshot.
An issue can be logged on a source file or a unit test file.