Message-ID: <1809410308.953.1394425707019.JavaMail.firstname.lastname@example.org> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_952_2067221982.1394425707018" ------=_Part_952_2067221982.1394425707018 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
To collect C++ test coverage metrics with C++ Community Plugin, = you have to:
Three types of test coverage are supported: Unit, Integrati= on and Overall coverage. Use one of the following&nb= sp;configuration pro= perties dependent of the coverage type (see also Configuration for details):
SonarQube <3.2 provides metrics= for line coverage and branch coverage. Bullseye users have function and br= anch/decision coverage instead. The C++ Community plugin converts the secon= d directly into branch coverage however line coverage is far more complex a= nd cannot be correlated directly into function coverage.= p>
Line coverage imported from a bull= seye report means than function coverage + line branch coverage (this secon= d occurs since SonarQube will not display branch coverage if there isn= 't a line it associated with it). This means also that overall coverag= e will be affected in SonarQube and cannot be compared directly to bullseye= results. The following pictures illustrate this for a small example projec= t.