The Firefox code coverage diff viewer allows determining code coverage changes for added lines per changeset.
Перейти к файлу
Armen Zambrano G 36f362f726 Issue #141 - Generate source maps for production 2018-03-08 15:24:07 -05:00
src Issue #139 - Use sentry.io to track frontend runtime issues 2018-03-08 12:19:39 -05:00
.babelrc chore: Add bable-cli and babel-preset-flow as dev dependencies 2017-09-13 15:40:58 -04:00
.eslintrc.js Issue #98 - Switch from react-scripts to Neutrino (#109) 2018-02-09 08:37:49 -05:00
.flowconfig chore: Add Flow's statistical analysis 2017-09-14 13:34:37 -04:00
.gitignore Bootstrap project with Neutrino 2017-08-02 16:21:29 -04:00
.neutrinorc.js Issue #141 - Generate source maps for production 2018-03-08 15:24:07 -05:00
.travis.yml Issue 26 - Travis support with linting check 2018-01-29 10:06:44 -05:00
CONTRIBUTING.md docs - Add note on how to keep branch up-to-date 2018-01-29 10:26:19 -05:00
LICENSE Initial commit 2017-07-19 12:44:33 -04:00
README.md docs - Link to overall architecture of Mozilla's code coverage blog post (#95) 2018-01-22 16:21:51 -05:00
app.json Issue #98 - Switch from react-scripts to Neutrino (#109) 2018-02-09 08:37:49 -05:00
package.json Issue #139 - Use sentry.io to track frontend runtime issues 2018-03-08 12:19:39 -05:00
static.json Changes to allow deployments via Heroku 2017-09-05 14:22:44 -04:00
yarn.lock Issue #139 - Use sentry.io to track frontend runtime issues 2018-03-08 12:19:39 -05:00

README.md

Firefox code coverage diff viewer

This project is the code coverage changeset viewer for Firefox. You can view the frontend running in here.

To understand the big picture of code coverage at Mozilla read this blog post.

The app will show recent changesets from mozilla-central that have code coverage (pending changesets will be automatically be fetched). From there you can navigate to the diff of each changeset and see the code coverage for added lines. It is very important to reiterate that it is code coverage for added lines and not for a specific file (as most code coverage viewers focus on).

The data used in this UI is based on data submitted to codecov.io.

Planning and views

This is document tracks the original plans while these track grid view of plans and long term plans. You view all coverage collection work tracked in here. You can preview this app here while over here we track files without any coverage.

Disclaimers

  • Linux64 only
    • partial debug build type: some flags are disabled
    • debug only tests are run
  • A few tests are disabled on coverage builds due to high failures
  • We ignore C++ files generated from IDL, IPDL, WebIDL
  • Coverage collections are for .c*, .h*, and .js* files
    • However, not all of these are covered (either no coverage or zero coverage)
    • Some of these are because we don't cover all platforms
  • Intermittent failures during testing cause different code paths to be hit (such as crash reporting)
  • Broken builds/failures might prevent us from running a test, set of tests, or a few jobs, coverage could be abnormally low

Filing issues

You can file frontend issues in Firefox code coverage frontend. For backend issues file them in releng-services with the 4.app: shipit_code_coverage label.

Requirements

Set up

Checkout the code and run:

yarn install
yarn start