Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

--file can only configure file name. It is not possible to give a full path. Resulting file will be in working directory with name <filename>.nccov (coverage-report.nccov in our example).

...

SonarQubeTM Integration, Step #1

  • ask people to configure NCover project by themself
  • add a new parameter sonar.ncover4.projectName that user should provide for each project
  • add a new parameter sonar.ncover4.installDirectory
  • run:
Code Block
languagepowershell
<sonar.ncover4.installDirectory\NCover.exe> Run --project=<sonar.ncover4.projectName> --buildId=<timestamp> -- <current Gallio command line>

...

Limitations: manual configuration step required. No guaranty that NCover configuration (especially module names) match Sonar matches SonarQubeTM configuration (exclusions, ...). No way to differentiate Unit tests and ITs.

...

SonarQubeTM Integration, Step #2

TODO find a way to automatically verify configuration of NCover project. Then create or update NCover project if necessary. Require an API. Question asked to NCover support. In this case we could make parameter sonar.ncover4.projectName optional (and automatically generate a project name during first execution and reuse it later).

...

SonarQubeTM Integration, Step #3

Run 2 executions of Gallio/NCover in order to separate unit tests and ITs. Question: should we have 2 separate projects in NCover Code Central or does 1 project for both is fine? With second option I fear history in Code Central will be broken as we will have alternatively

...