Full documentation for SonarQube has moved to a new location: http://docs.sonarqube.org/display/SONAR

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

ConceptDefinitionRelated Topics
Check

Check = Coding Rule.

 
Anchor
codingRule
codingRule
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
Anchor
resource
resource
Component
A piece of software (project, module/package, file) or a view or a developer. 
Anchor
metric
metric
Metric

A property of a component. Examples: number of lines of code, complexity, etc.

A metric may be either:

  • qualitative: gives a quality indication on the component (ex: density of duplicated lines, line coverage by unit tests, etc.)
  • or quantitative: does not give a quality indication on the component (ex: number of lines of code, complexity, etc.)

The value of the metric for a given component is called measure.

See detailed documentation on metrics.
Anchor
measure
measure
Measure

The value of a metric for a given component at a given time.

Examples:

  • 125 lines of code on class MyClass
  • Density of duplicated lines of 30.5% on project myProject
 
Anchor
qualityProfile
qualityProfile
Quality Profile

A set of coding rules.

Each snapshot is based on a single quality profile.

See Quality Profiles.
Anchor
snaphshot
snaphshot
Snapshot

A set of measures and issues on a given component at a given time.

A snapshot is generated for each analysis.

 
Anchor
issue
issue
Issue

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.

 

...