Closed timotheecour closed 5 years ago
@timotheecour coverage/
in this repo is only used as an example of the report generated by Coco.
About --report_path
it does the job correctly, cleanup then creating the report at that path. When you ran the command ./coco
, it ran my tests and one was removing coverage/
. Totally unnecessary and confusing. It's fixed now.
Agree about git status
. It should stay clean as much as possible. Now, by default, you should only get 1 directory with the HTML report (I should add an option to disable the generation) and your LCOV file. This one is really useful in your project as it's read by Coverage Gutters in VSCode.
running
./coco
shouldn't affectgit status
;coverage
is removed even though I specified ./coco --report_path=/tmp/d19 so I'd assume it'd instead remove /tmp/d19I'm actually confused about
coverage
; was this intended to be checked in this repo or was it an artifact of running./coco
and checking in automatically generated files in the repo? if the latter, these should be deleted from this repo even after removingcoverage
,./coco
still works which makes me think snow.png (etc) are generated by something else (maybe lcov?)I really like when
git status
stays clean after running commands (or at least everything generated goes under 1 directory); maybe 1 option is to generate:under a
build/
dir that's gitignored?