Google Git
Sign in
gerrit / plugins / code-coverage / 75a7ab810abf90b1c1f6efa3a5f79f5525e2854f
commit75a7ab810abf90b1c1f6efa3a5f79f5525e2854f[log] [tgz]
authorTiago Quelhas <tjgq@google.com>Tue May 04 12:29:32 2021 -0700
committerTiago Quelhas <tjgq@google.com>Tue May 04 12:30:01 2021 -0700
tree836a13d63f5292e3302b28527e10d97461d8d046
parent27b26fdc57bf7702891c30dc5e3041e6c6b75216 [diff]
Add a dummy export statement to files imported as ES modules.

Inside Google, we are making it a requirement for files that are imported using ES syntax to be "marked" with an import or export statement.

Change-Id: I0fd3b2b58cc08c35c156c67edf9323decca3b8d5
1 file changed
tree: 836a13d63f5292e3302b28527e10d97461d8d046
  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