Would be interesting to see if we can set this up for c-c as well.
Philipp
Begin forwarded message:
From: Marco Castelluccio mcastelluccio@mozilla.com
Date: 15. July 2019 at 5:55:50 PM CEST
To: dev-platform dev-platform@lists.mozilla.org, Firefox Dev firefox-dev@mozilla.org
Subject: New coverage frontend and zero coverage checker
Hello everyone,
We are switching from relying on codecov.io and coveralls.io to our own
backend/frontend to handle coverage data.
This will allow us to build more features such as filtering coverage
results by OS, filtering by test suite, etc..
Moreover, codecov.io and coveralls.io were not able to handle the load
of our large repositories. With a custom backend, we now have consistent
performance.
The code coverage reports now live at
https://mozilla.github.io/code-coverage-reports/ (the URL might change,
but we will setup a redirect if it does).
You can see a graph of the coverage over time (clicking on one of the
points of the graph will bring you to that revision), see coverage
summaries by directory, see source code with coverage highlight (green
for covered, red for uncovered).
In a few days, we will stop uploading coverage data to codecov.io and
coveralls.io.
On a related note, we have recently enabled a new checker in our Review
Bot which will warn you if one of the files in your patch is completely
uncovered by tests (which might mean that the file should be tested,
https://bugzilla.mozilla.org/show_bug.cgi?id=untestedcode-codecoverage,
or that the file is dead code,
https://bugzilla.mozilla.org/show_bug.cgi?id=deadcode-codecoverage, or
that it is tested in a configuration which is not yet supported by code
coverage). As usual, you can also browse our full zero coverage report
at
https://mozilla.github.io/code-coverage-reports/zero_coverage_report.html.
- Marco, on behalf of the team (special thanks to Bastien who has been
doing most of the work on the new backend/frontend).
firefox-dev mailing list
firefox-dev@mozilla.org
https://mail.mozilla.org/listinfo/firefox-dev
Would be interesting to see if we can set this up for c-c as well.
Philipp
Begin forwarded message:
> From: Marco Castelluccio <mcastelluccio@mozilla.com>
> Date: 15. July 2019 at 5:55:50 PM CEST
> To: dev-platform <dev-platform@lists.mozilla.org>, Firefox Dev <firefox-dev@mozilla.org>
> Subject: New coverage frontend and zero coverage checker
>
> Hello everyone,
> We are switching from relying on codecov.io and coveralls.io to our own
> backend/frontend to handle coverage data.
> This will allow us to build more features such as filtering coverage
> results by OS, filtering by test suite, etc..
> Moreover, codecov.io and coveralls.io were not able to handle the load
> of our large repositories. With a custom backend, we now have consistent
> performance.
>
> The code coverage reports now live at
> https://mozilla.github.io/code-coverage-reports/ (the URL might change,
> but we will setup a redirect if it does).
> You can see a graph of the coverage over time (clicking on one of the
> points of the graph will bring you to that revision), see coverage
> summaries by directory, see source code with coverage highlight (green
> for covered, red for uncovered).
> In a few days, we will stop uploading coverage data to codecov.io and
> coveralls.io.
>
> On a related note, we have recently enabled a new checker in our Review
> Bot which will warn you if one of the files in your patch is completely
> uncovered by tests (which might mean that the file should be tested,
> https://bugzilla.mozilla.org/show_bug.cgi?id=untestedcode-codecoverage,
> or that the file is dead code,
> https://bugzilla.mozilla.org/show_bug.cgi?id=deadcode-codecoverage, or
> that it is tested in a configuration which is not yet supported by code
> coverage). As usual, you can also browse our full zero coverage report
> at
> https://mozilla.github.io/code-coverage-reports/zero_coverage_report.html.
>
> - Marco, on behalf of the team (special thanks to Bastien who has been
> doing most of the work on the new backend/frontend).
>
> _______________________________________________
> firefox-dev mailing list
> firefox-dev@mozilla.org
> https://mail.mozilla.org/listinfo/firefox-dev