| commit | bc5ef6ed320c6c78527a7a695b39291b4d6b7810 | [log] [tgz] |
|---|---|---|
| author | Prakhar <pasthana@google.com> | Wed Feb 16 17:58:55 2022 |
| committer | Prakhar Asthana <pasthana@google.com> | Wed Feb 16 19:03:59 2022 |
| tree | 6b108260caef6a462bc954e38926ed119c5531a1 | |
| parent | bfee431e160409b7f01e4149f242805373f60630 [diff] |
Increase thresholds for low coverage warning Bug: 1298136 Change-Id: I352ee10dc0def7d7424fc40b066b7b9fb3ad41e1
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
bazel test web:karma_test
For testing the plugin with Gerrit FE Dev Helper build the JavaScript bundle and copy it to the plugins folder:
bazel build plugins/code-coverage/web:code_coverage cp -f bazel-bin/plugins/code-coverage/web/code_coverage.js plugins/chromium-coverage.js
and let the Dev Helper redirect from .+/plugins/code-coverage/.* to http://localhost:8081/plugins_/chromium-coverage.js
You might also have to block loading of prod coverage plugin(s) by using a block rule similar to .*polygerrit_assets/549.0/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