Add coverage report for unit tests
What does this MR do?
Adds coverage report to unit tests jobs. It also adds -v
, so it's easier to find which output is related to which test being executed (which is usefule for some failures)
Why was this MR needed?
Are there points in the code the reviewer needs to double check?
Does this MR meet the acceptance criteria?
-
Documentation created/updated - Tests
-
Added for this feature/bug -
All builds are passing
-
-
Branch has no merge conflicts with master
(if you do - rebase it please)
What are the relevant issue numbers?
Edited by Tomasz Maczukin