Skip to content
Snippets Groups Projects
Commit b69bf110 authored by Arin Wongprommoon's avatar Arin Wongprommoon
Browse files

[WIP] ci: measure branch coverage

WHY IS THIS CHANGE NEEDED?:
- branch coverage give additional information re test coverage -- more
  informative for writing tests

HOW DOES THE CHANGE SOLVE THE PROBLEM?:
- add --branch flag, according to https://coverage.readthedocs.io/en/7.0.4/branch.html#how-to-measure-branch-coverage

WHAT SIDE EFFECTS DOES THIS CHANGE HAVE?:
- will change the coverage report and the final percent coverage

REFERENCES:
- issue #46
- merge request !8
parent 24fc0935
No related branches found
No related tags found
No related merge requests found
...@@ -38,7 +38,7 @@ Local Tests: ...@@ -38,7 +38,7 @@ Local Tests:
stage: tests stage: tests
script: script:
# - poetry install -vv # - poetry install -vv
- poetry run coverage run -m pytest ./tests --ignore ./tests/aliby/network --ignore ./tests/aliby/pipeline - poetry run coverage run -m --branch pytest ./tests --ignore ./tests/aliby/network --ignore ./tests/aliby/pipeline
- poetry run coverage report -m - poetry run coverage report -m
- poetry run coverage xml - poetry run coverage xml
coverage: '/(?i)total.*? (100(?:\.0+)?\%|[1-9]?\d(?:\.\d+)?\%)$/' coverage: '/(?i)total.*? (100(?:\.0+)?\%|[1-9]?\d(?:\.\d+)?\%)$/'
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment