Skip to content
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

Console reporter #117

Closed
resah opened this issue Jun 27, 2018 · 3 comments
Closed

Console reporter #117

resah opened this issue Jun 27, 2018 · 3 comments
Assignees
Milestone

Comments

@resah
Copy link

resah commented Jun 27, 2018

Is it possible to write code coverage information to console?

We are using GitLab-CI, which reads coverage information from console output during build and shows this directly in related merge requests.

Right now I am using jacoco and would love to switch to this awesome clover plugin.

@Alex-Vol-SV
Copy link
Collaborator

If you enable XML report you can probably create a new task that uses XMLSlurper to pick the values out of the XML report and print them. Instead of just running the cloverGenerateReport or cloverAggregateReports task you would run your own task which would depend on either of the above as needed and then would pick the values out of the clover.xml summary. You would do that to print the desired values as part of the task action.

I could add that feature in the clover tasks either as what I just described or some more internalized functionality that possibly works even with XML report disabled. Although, I am not sure there is a proper API to get the necessary information from clover without enabling the report to use XML.

@khamburg-dev
Copy link

plus 1. I would like to be able to show the coverage percentage in the build console output without having to open the report.

@Alex-Vol-SV Alex-Vol-SV added this to the 2.2.3 milestone Oct 16, 2019
@Alex-Vol-SV
Copy link
Collaborator

Added console reporter feature when XML reports are used. The feature is activated automatically when the XML report is generated.

See update in README

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants