Message-ID: <1943884814.965.1427559103449.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_964_1413670225.1427559103449" ------=_Part_964_1413670225.1427559103449 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
The component viewer is the heart of SonarQube: it displays the source c= ode of a file (both source and test files), and all relevant information ab= out it:
You will land on the component viewer:
The component viewer is composed of 3 parts:
The header can contain up to 5 tabs, one per main axis: Overall Measures, Technical Debt and Issues, Coverage= (for source files) or Tests = a>(for test files), Duplications, an= d SCM. Tabs which aren't relevant to= the current file won't be shown. For instance, if the project has no tests= , the coverage tab will be omitted. Similarly, the duplications tab will be= omitted if there are no duplications, and the SCM tab will be missing if t= he relevant plugin is not installed.
You can click on each tab to show its detailed metrics in a row below th= e tabs. Click the same tab again to toggle display of the metrics row.
Each tab consists of two parts: a thin blue line at the top, which contr=
ols decoration, and the tab itself, which controls
On top of each tab (except the first one), a light blue bar can be toggl= ed to activate decoration of the source code wit= h information relevant to the tab.
When a tab is expanded, it gives access to filtering action= s:
Decoration and filtering work independently of each other. For inst= ance, it's possible to filter the source code to see only the parts where t= here are info issues, while keeping the coverage information displayed on t= hose lines - like in the example below:
If you click on one of the filters available on the Issue, Coverage, or = Duplication tabs, the component viewer automatically toggles the appropriat= e decoration for you if it's not already active.
The workspace keeps track of your navigation history when you use t= he features of the component viewer itself to navigate between files. It ca= n help you:
Note that the workspace is automatically cleaned up once you stop naviga= ting through these 2 features.
The main purpose of the component viewer is to show source code:
To learn more about the decorating and filtering capabilities of each of= the header tabs, please see