diff options
| author | Cole Robinson <crobinso@redhat.com> | 2020-02-02 08:24:36 -0500 |
|---|---|---|
| committer | Cole Robinson <crobinso@redhat.com> | 2020-02-03 07:05:11 -0500 |
| commit | 226c25b07d98b4fb42e8941dbdc616294d9a5723 (patch) | |
| tree | 15b945993d122a438db148b70f4cbebdbdf76887 /CONTRIBUTING.md | |
| parent | 67ef81895e925b8ec58e8b5f59e348baa12ce640 (diff) | |
| download | virt-manager-226c25b07d98b4fb42e8941dbdc616294d9a5723.tar.gz | |
CONTRIBUTING: Add note that test coverage shouldn't regress
Signed-off-by: Cole Robinson <crobinso@redhat.com>
Diffstat (limited to 'CONTRIBUTING.md')
| -rw-r--r-- | CONTRIBUTING.md | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index c5505130..cc55aba6 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -38,6 +38,11 @@ and [`pycodestyle`](https://github.com/pycqa/pycodestyle) to be installed. If [`codespell`](https://github.com/codespell-project/codespell) is installed, it will be invoked as well. +Patches to `virtinst/` code should ideally not regress code coverage +testing. Run `./setup.py test --coverage` to see a coverage report +before and after your contribution, and ensure no new lines show up. +Maintainers can help you out if you aren't sure how to test your code. + One useful way to manually test virt-manager's UI is using libvirt's unit test driver. From the source directory, Launch virt-manager like: ```sh |