-
Notifications
You must be signed in to change notification settings - Fork 15
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
Istanbul (Node) Coverage Reporting #3
Conversation
@ksoichiro Could you please give feedback on this PR? |
Rebranded project as bti for maven publishing Using gitlab-ci to publish Removed old build tools Updated readme Made release manual and publish only on master Fixed properties and build
Sorry for my late reply. How do I confirm your reporter in your sample? I tried |
Hey, thanks for your response! If I remember correctly, that is how I executed it. I forked the project and further developed it for our needs. I do recall fixing something to get the report on that (though I remember it working for this PR). I won't have time today to get to it, but I will try to get back to you ASAP. Here is the fork of your project: https://gitlab.com/bti360/gradle-console-reporter |
I closed this since the changes that worked were not made in the master branch. I will make a new PR with the proper changes. |
Sorry for the confusion. I created a new PR: #4 |
This adds capabilities for reporting coverage for the Node reporting tool Istanbul.
http://gotwarlost.github.io/istanbul/