*# Q3 Codecoverage! update * /If you //want to hear more about an//y of the//s//e items, please contact me and I will get you more detailed information/* *
*## Overview * We can show the code coverage on new lines added by changeset! * *Link* - http://firefox-code-coverage.herokuapp.com/ * *Warning* - This is alpha-quality; it is a work-in-progress, there are still bugs, and it is not as responsive as we would like * *Visual walk through* - https://github.com/armenzg/firefox-code-coverage-frontend/raw/7b67f2e948de94b7f837ba9a7c57a31e810d9fe7/docs/Prototype%20Instructions.pdf Of course, we still have the regular coverage that we upload to codecov.io [4] https://codecov.io/gh/marco-c/gecko-dev *## Parts you don't see* * *Keep the tests passing* - Code coverage builds run a little different, so we must constantly monitor and triage the unique test failures. * *Building the backend for the UI* - The UI is supported by a backend service that maps coverage to the changesets * *optimize jsvm lcov rewriter* - because everything is slow at our scale of coverage * *merge coverage from test chunks* - because codecov.io can not handle our raw data volume * *adding function info to grcov *- a different resolution of coverage that is consistent with other coverage tools * *Rust LLVM build* - We require a special build of Rust in order to collect Rust coverage; https://treeherder.mozilla.org/#/jobs?repo=try&revision=014e361716000d0dee4427bf7195316a2aba7b21 *## Future Plans* * *Verify this UI prototype* - We want to ensure RelMan can use this to inform their bug risk assessment * **Improve the UI* - *There are inevitable changes to be made when we get our feedback from RelMan, plus the known bugs and issues we need to work on. * * *Coverage for Windows with Clang* - https://bugzilla.mozilla.org/show_bug.cgi?id=1381163 * *Solve bugs* - Of course, there is a long tail of bugs * *Show what tests cover a file* - Experimental - a couple UCOSP students will attempt to show coverage at the per-test level; this should prove useful to those that made a code change, and would like to know what test suite (or test chunk) covers it. If useful, then we can use this same information to inform our automation. * *Merge coverage from different revisions* - Experimental - a UCOSP student will attempt a pan-temporal representation of our source code: If done, it will allow us transport code coverage forward, and backward, through time and revisions. This can be used to compare coverage runs, merge runs from different revisions, and allow us to collect coverage at a higher resolution with lower data storage costs. *## Meetings* We have weekly CodeCoverage meetings, and you are welcome to attend: * *When* - Held every Friday @ 11:30 EDT (08:30 PDT) * *Where* - Kyle's video room https://v.mozilla.com/flex.html?roomdirect.html&key=huhL8WaTwCwC * *Etherpad* - https://public.etherpad-mozilla.org/p/code_coverage_Q1_17 *## Links* [1] The frontend UI http://firefox-code-coverage.herokuapp.com/ [2] Frontend code https://github.com/armenzg/code_cov_experiments [3] Backend server https://github.com/mozilla-releng/services/tree/master/src/shipit_uplift/shipit_uplift [4] Total Coverage https://codecov.io/gh/marco-c/gecko-dev [5] UCOSP - http://ucosp.ca/ _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
