This repository has been archived by the owner on Jul 8, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 105
SonarTsPlugin not attempting to load LCOV coverage file #177
Comments
Are you sure that you have installed TypeScript plugin from Pablissimo and not from SonarSource? |
I have the same issue using the extension
Unfortunely the lcov.info is never picked up. I tried a different approach with a single module setup, but the outcome was the same. |
Worked for me to use this property to define paths as documented here.. |
Thanks @lillicrm , this helped! Unfortunately this property is called differently on https://github.com/Pablissimo/SonarTsPlugin , which caused the problems and confusion. I guess the readme file should be updated. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello,
Firstly, thanks for the great plugin. It's really useful, just have one small problem to do with code coverage. I'm using SonarQube Scanner 3.0.3.778, SonarTS 1.0.0.340 and SonarQube server 6.5.0.
I can't seem to get the plugin to load my lcov.info coverage file that my unit test pipeline (Karma -> remap-istanbul) has output. I have tried setting
sonar.ts.coverage.lcovReportPath=lcov.info
but it doesn't appear to be using it. I have the following two reasons to believe this:sonar-scanner -X
show the step taking 0ms, which seems suspiciously fast to load and parse a file.sonar.ts.coverage.lcovReportPath=lcov.info
I see no hits to the file system. I ran another test with the following config......because I wanted to see (a) if my process monitor filter ('lcov') was working, and (b) to see if any of the others settings would work instead. Process Monitor successfully recorded a file system hit for the
lcov.info4
file, which meanssonar.javascript.lcov.reportPaths=lcov.info4
was getting picked up, but coverage is still at 0%. So I know my settings file is working, and I know TsPlugin didn't attempt to hit the file system.I don't have any errors in the logs. There's a bunch of warnings but TBH they look unrelated. The analysis is otherwise getting reported and working well in SonarQube.
If you have any ideas that would be much appreciated. Thanks in advance! Chris
The text was updated successfully, but these errors were encountered: