Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

ConceptDefinitionRelated Topics
Check

Check = Coding Rule.

 
Client

Batch that runs source code analyzers to compute snapshots.

See Architecture Overview.
Coding RuleA good coding practice. Violating coding rules leads to quality flows. 
Database

Stores:

See Architecture Overview.
Metric

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

A metric may be either:

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

The value of the metric for a given Sonar Concepts is called Sonar Concepts.

See detailed documentation on metrics.
Measure

The value of a Sonar Concepts for a given Sonar Concepts at a given time.

Examples:

  • 125 lines of code on class myClass
  • Density of duplicated lines of 30.5% on project myProject
 
Quality Profile

A set of coding rules.

Each Sonar Concepts is based on a single quality profile.

 
ResourceA piece of software. Examples: project, package, module, file, etc. 
Server Web Server that is used to navigate the snapshots and make configurationSee Architecture Overview .
Snapshot

A set of measures and violations on a given Sonar Concepts at a given time.

A snapshot is generated for each Sonar analysis.

 
Violation

When a Sonar Concepts does not comply with a coding rule, Sonar logs a violation to the Sonar Concepts.

 
  • No labels