internet/kubevirt.core
3
0
Fork 0
mirror of https://github.com/kubevirt/kubevirt.core.git synced 2026-03-26 19:03:16 +00:00
Code Issues Packages Projects Releases Wiki Activity

Add documentation running coverage analysis.

Browse Source 
It documents how the coverage analyzer can be used to create a test
coverage report.

Signed-off-by: Javier Cano Cano <jcanocan@redhat.com>
This commit is contained in:
Javier Cano Cano
2024-07-01 15:40:23 +02:00
parent 65f4ac6602
commit a6ef7e9a5a
1 changed files with 26 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

26
docs/testing.md
View File

@@ -53,6 +53,32 @@ Run unit tests with `ansible-test` like so:
ANSIBLE_TEST_PREFER_PODMAN=1 ansible-test units --docker ANSIBLE_TEST_PREFER_PODMAN=1 ansible-test units --docker
``` ```
### Running tests with coverage analysis
Coverage analysis produces a report about the code paths covered by the unit tests.
It is required to bind mount the project as shown in section [Running tests with ansible-test](#running-tests-with-ansible-test).
Run `ansible-test` with:
```
ANSIBLE_TEST_PREFER_PODMAN=1 ansible-test units --docker --coverage
```
Create the coverage report in HTML format using:
```
ansible-test coverage html
```
Or in XML format using:
```
ansible-test coverage xml
```
Multiple coverage report formats are supported such as: plain text, XML or HTML. If HTML format is used as shown above, the report can be accessed in the following location: `~/.ansible/collections/ansible_collections/kubevirt/tests/output/reports/coverage/index.html` or in `~/.ansible/collections/ansible_collections/kubevirt/tests/output/reports/coverage/coverage.xml` if XML format is choosen.
## Integration tests ## Integration tests
Integration tests require a working cluster and can be run with Integration tests require a working cluster and can be run with