| commit | bb3d39ed6baf64a91d3d806f0ad9d19b882326b3 | [log] [tgz] |
|---|---|---|
| author | Prakhar <pasthana@google.com> | Mon Jan 29 16:14:30 2024 |
| committer | Prakhar Asthana <pasthana@google.com> | Mon Jan 29 16:18:36 2024 |
| tree | 375224056850bd55cce6be05088b0e4d72bc14f4 | |
| parent | f4d3a2f94a795c7cb1e46087b49d355860fd4527 [diff] |
Improve messaging of coverage warning Bug: 1494235 Change-Id: I19cc3786440ae6698773f17d491dfed884f20aa8
The purpose of this plugin is to surface code coverage data on Gerrit UI.
To check out the chromium-coverage plugin code, first make sure you have gerrit frontend code checked in
git clone https://gerrit.googlesource.com/gerrit
cd into plugins directory and checkout this repo
cd plugins/ git clone https://chromium.googlesource.com/infra/gerrit-plugins/code-coverage
Following commands assume you have cd'ed into web/ directory
make test
For testing the plugin with Gerrit FE Dev Helper
1. make build (This creates a chromium-coverage.js file inside plugins directory) 2. cd ../../.. (cd into gerrit frontend code dir) 3. npx http-server -c-1 --cors
and let the Dev Helper redirect from .+/plugins/chromium-coverage/.* to http://localhost:8080/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