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 61 Next »

Table of Contents

Analysis Modes

AnalysisStandard way to analyze the source code. The source code is analyzed and measures and issues are pushed to the SonarQube database. The results of the analysis can be browsed through the web interface.

The source code is analyzed but the measures and issues are not pushed to the SonarQube database. Therefore, they cannot be browsed through the web interface. This mode can be used with the Issues Report plugin, which generates an HTML issues report to local file.

IncrementalSame as Preview mode but only new or modified files (compared to the latest version available on the remote server) are analyzed. This is the default mode of the SonarQube Eclipse plugin.


ConceptDefinitionRelated Topics
AnalyzerA client application that analyzes the source code to compute snapshots.See the SonarQube Platform Overview.


  • configuration
  • snapshots
See the SonarQube Platform Overview.
Server Web interface that is used to browse snapshot data and make configuration changesSee the SonarQube Platform Overview.



ConceptDefinitionRelated Topics

Check = Coding Rule.

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 Perspective
ComponentA piece of software (project, module/package, file) or a view or a developer. 

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.


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


  • 125 lines of code on class MyClass
  • Density of duplicated lines of 30.5% on project myProject

A type of measurement. 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.
Quality Profile

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.

Non-functional requirementNon-functional requirement = coding rule 

Web Interface

ConceptDefinitionRelated Topics

Web page that provides a way to display any data stored in the database.

A dashboard is a set of widgets.

See Project Dashboards, Global Dashboards


It is a box that displays data on a dashboard.

There are two types of widget:

  • Global widget - displays data from multiple projects
  • Project widget - displays data from a specific project


DrilldownA file-specific presentation of measure data. Some metrics have specialized presentations. 
  • No labels