Would be better to have coverage settings for integration test.

[andy-maca]

Hi,

With javascript sonar plugin, there's an option 'sonar.javascript.lcov.itReportPath' used for setting coverage for integration test, so it would be great to have this option for typescript too, like 'sonar.ts.lcov.itReportpath'.

[Pablissimo]

Agree entirely - it should do exactly what the JavaScript one does, and the refactoring on the back of the SonarQube 6.0 support should make it a bit easier to accomplish. Will look at this when next have a chance (or submit a pull).

[pyrocks]

Isn't this a duplicate to the enhancement request in https://github.com/Pablissimo/SonarTsPlugin/issues/44 ? Just wondering... :) Edit: maybe this is for integration and the #44 is for unit

[Pablissimo]

It's related but not quite the same - the JavaScript plugin supports supplying code coverage metrics split out by code covered by unit tests and code covered by integration tests (rather than the unit-test-only metric the SonarTsPlugin currently supports). This is asking for feature parity with the JavaScript plugin, to be able to report coverage as a result of an integration test. #44 is asking for supporting parsing of something that gives the number of tests and results of those tests.

Coverage files don't give that, and you can easily get 100% coverage with an entirely failing test suite!