|author||Tiago Quelhas <firstname.lastname@example.org>||Tue May 04 12:29:32 2021 -0700|
|committer||Tiago Quelhas <email@example.com>||Tue May 04 12:30:01 2021 -0700|
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
The purpose of this plugin is to surface code coverage data on Gerrit UI.
To check out the chromium-coverage plugin code:
git clone https://chromium.googlesource.com/infra/gerrit-plugins/code-coverage
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.
ln -s /path/to/chromium-coverage.html plugins/
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