Message-ID: <16096135.4754.1422535040546.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_4753_1086839531.1422535040545" ------=_Part_4753_1086839531.1422535040545 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
|Analysis||Standard way to analyze the source= code. The source code is analyzed and measures and issues are pushed to th= e SonarQube database. The results of the analysis can be b= rowsed through the web interface.|
The source code is analyzed but= the measures and issues are not pushed to the SonarQube database= strong>. Therefore, they cannot be browsed through the web interface. This mode can be used with the Issues Report plugin, which generat= es an HTML issues report to local file.
|Incremental||Same as Preview mode but onl= y new or modified files (compared to the latest version available on the re= mote server) are analyzed. This is the default mode of the SonarQube Eclipse plugin and the SonarQube IntelliJ plugin.|
|Analyzer||A client application that analyzes= the source code to compute snapshots.<= /span>||See the SonarQube Platform Overview.|
|See the SonarQube Platform Overview.|
|Server||Web interface that= is used to browse snapshot data and make configuration ch= anges||See the SonarQube Platform Overview.|
Check =3D Coding Rule= strong>.
A good coding practice. Not com= plying to coding rules leads to quality flaws and creation of issues in Son= arQube.
Coding rules can check quality on files, unit tests or packag= es.
|See Viewing Unit Tests > Issues Perspective|
|Component||A piece of software (project, module/package, fi= le) 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= strong> for a given component at a given time.
A type of measurement. Metrics can have varying values, or mea= sures, over time. Examples: number of lines of code, complexity, etc.
A metric may be= either:
|See detailed documentation on metrics.|
A set of coding rules= strong>.
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 requirement=||Non-functional requirement =3D
Web page that provides a way to= display any data stored in the database.
A dashboar= d is a set of widgets.
It is a box that displays data = on a dashboard.
There are two types of widget:
|Drilldown||A file-specific presentation of