-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is there any way to see the class coverage over xml report #271
Comments
Hi, |
@shanshin , I am referring to the HTML from Kover. Let me elaborate a little bit more. I am using the XML report for reporting coverage from Jenkins. Meaning, I am running the
But when I got in Jenkins to Coverage Report -> File Coverage I cannot click on a file to see what are the lines that are covered and what are not. I cannot have a visual input about what is tested. Is there a way to do this? |
Unfortunately, compatibility with Jenkins is not guaranteed at the moment. Could you provide an XML report that is displayed correctly in Jenkins and a Kover report for which no file is generated? |
@shanshin , the reports were generated with So I am assuming the default settings for this are not showing the same output or maybe not in the format in which Jenkins can interpret them and show the covered lines. |
Closed as duplicate of #272 |
Hi!
I am interested in looking to see if there is a way to display the coverage at a file level in an HTML representation from the XML report.
Right now, we are using Jacoco and Jenkins Jacoco plugin to display the coverage on each PR. This means that we can break down to classes and see an html representation of what lines are covered in a file and what are not.
Trying Kover, I found out that we can no longer see this on the XML report. The files cannot be opened to see the actual lines that are covered by tests and the ones that are not.
Is there a way to configure Kover to include an html representation in the XML report? Or can we achieve this somehow?
Also, can we integrate this with Sonarqube? Right now we are facing the same problem with lines not being displayed for coverage in Sonarqube.
Thank you!
The text was updated successfully, but these errors were encountered: