Message-ID: <448604884.843.1427910992163.JavaMail.email@example.com> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_842_890861224.1427910992163" ------=_Part_842_890861224.1427910992163 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Current status: NOT IMPLEME= NTED
Feel free to vote for SONARDOTNT-275
There is no longer a Gallio-specific runner for NCover 4 (/r:NCover3). N= Cover 4 can monitor any .NET program and collect coverage. The requirement = is to configure a project in NCover Code Central and tell it what process t= o monitor (name or regexp of process name), and also add some filters to te= ll what modules are associated with the project.
Here is a sample configuration:
Once a project is configured in Code Central, measures will be automatic= ally collected the next time a monitored program is run.
In order to start a coverage session and collect resulting data in the N= Cover 3 XML format, here are the commands you should run:
This first command will associate the collected data to a buildId (TODO = ask NCover support what are the constraints on the buildId).
Then to retrieve data:
--execution value should match value provided in the previous --buildId<= /p>
--file can only configure the file name. It is not possible to give a fu= ll path. Resulting file will be in working directory with name <filename= >.nccov (coverage-report.nccov in our example).
sonar.ncover4.projectNamethat the use= r should provide for each project
Limitations: manual configuration step required. No guarantee that NCove= r configuration (especially module names) matches SonarQube configuration (= exclusions, ...). No way to differentiate Unit tests and ITs.
TODO find a way to automatically verify configuration of NCover project.=
Then create or update NCover project if necessary. Require an API. Questio=
n asked to NCover support. In this case we could make parameter
.ncover4.projectName optional (and automatically generate a project =
name during first execution and reuse it later).
Run 2 executions of Gallio/NCover in order to separate unit tests and IT= s. Question: should we have 2 separate projects in NCover Code Central or d= oes 1 project for both is fine? With second option I fear history in Code C= entral will be broken as we will have alternatively
Unit test --> ITs --> Unit test --> ITs --> ...
I fear option 1 will not work because with 2 projects configured to moni= tor Gallio.Echo.exe they will both be fed by coverage data (except if Run -= -project argument actually works).