Thanks to Andrew we’re now generating a test coverage report in Jenkins for
the katello on every PR and when code gets merged to master. We should be
able to track our code coverage over time using these reports and hopefully
it’ll improve our test coverage.
To view the coverage report for a PR, if you go to the test_katello_pr_core
job page, you should see a new icon on the left with the caption “Rcov
report”. If you click on that you should see a coverage report like this:
Just an addendum - we have http://codeclimate.com/ checking out our PRs
in Foreman core to provide stats about code 'cleanliness' - you can hook
it up to a test reporting tool so it automatically tells you on every PR
It'd free up some Jenkins resources & lists it separately in the PR so
you might want to consider it
The document you linked to sounds like they only integrate directly with a
handful of CI services but not Jenkins. It looks like they have a gem [1]
that would upload test coverage results but that won’t offload resources
from our Jenkins environment.
We have had code climate set up for a while for katello [2] and I’d love to
consider having it start checking PRs like we do on Foreman.
···
On Mon, Aug 8, 2016 at 5:05 AM, Daniel Lobato Garcia wrote:
On 08/05, David Davis wrote:
Thanks to Andrew we’re now generating a test coverage report in Jenkins
for
the katello on every PR and when code gets merged to master. We should be
able to track our code coverage over time using these reports and
hopefully
it’ll improve our test coverage.
To view the coverage report for a PR, if you go to the
test_katello_pr_core
job page, you should see a new icon on the left with the caption “Rcov
report”. If you click on that you should see a coverage report like this:
Just an addendum - we have http://codeclimate.com/ checking out our PRs
in Foreman core to provide stats about code ‘cleanliness’ - you can hook
it up to a test reporting tool so it automatically tells you on every PR
