Google Git
Sign in
gerrit / plugins / code-coverage / 27b26fdc57bf7702891c30dc5e3041e6c6b75216
commit27b26fdc57bf7702891c30dc5e3041e6c6b75216[log] [tgz]
authorTao Zhou <taoalpha@google.com>Thu Jul 23 14:35:10 2020 +0200
committerTao Zhou <taoalpha@google.com>Thu Jul 23 14:35:10 2020 +0200
treea1f9ad3e83d117acc496915e39d71ca8ca478433
parentb20fb17e51a94a2b92112c7e5993e8c0941a6651 [diff]
Replace @npm_bazel_rollup with @npm//@bazel/rollup

This is needed after we have rules_nodejs upgraded to 2.0

Change-Id: I2c49a8a4d8bd0fe225c5218e8683e0f0aaffd7de
1 file changed
tree: a1f9ad3e83d117acc496915e39d71ca8ca478433
  1. src/
  2. test/
  3. bower.json
  4. BUILD
  5. codereview.settings
  6. LICENSE
  7. package-lock.json
  8. package.json
  9. README.md
  10. wct.conf.json
README.md

Chrome/Chromium Code Coverage Plugin

The purpose of this plugin is to surface code coverage data on Gerrit UI.

Development

Checking out the code

To check out the chromium-coverage plugin code:

git clone https://chromium.googlesource.com/infra/gerrit-plugins/code-coverage

Running the tests

The unit tests of the plugin are web-component-tester unit tests. Dependencies are specified in bower.json and can be installed by running bower install in this directory. This requires bower to be installed.

To run the tests, run wct from this directory. See wct --help for more options.

To use with the local testsite

ln -s /path/to/chromium-coverage.html plugins/

Project Configuration

This plugin is configured via the project.config file present in the repo's refs/meta/config ref. This file uses git config format. By default, the coverage percentage columns in the file list are hidden to avoid visual distraction in unrelated projects, and in order to have them displayed, please add the following config:

[plugin "code-coverage"]
  enabled = true