Thanks for your help @slipset, I https://codecov.io/gh/clj-commons/rewrite-clj! And thanks @borkdude for the warning on PR comments, I configure those to off.
Nice!
Would you need to do this? https://docs.codecov.io/docs/fixing-paths
@slipset I donβt see an issue there for rewrite-clj, are you seeing a prob I might be missing? I use a kaocha plugin which uses cloverage. All the hard work is done by kaocha and cloverage for me.
https://codecov.io/gh/clj-commons/rewrite-clj/src/v1/src/rewrite_clj/paredit.cljc
I would expect to see some clojure code with some red/green/yellow stuff on it.
Ah thanks, I get the expected results on my screen from that URL, I shall take a deeper peek!
Itβs not very important π
Maybe not to you! simple_smile
But in general code coverage is not crazy important to me, but I do find the info interesting.
Test coverage can be a misleading metric. Such tools are only useful if you are doing something with this information, but how you should read these metrics is an art on its own. As such, I don't give it much value.
@slipset URL you shared is working for me without being logged in now, maybe http://codecov.io was just getting its act together.
Works now for me as well!
@borkdude, I mostly agree and https://github.com/clj-commons/rewrite-clj/blob/v1/doc/02-developer-guide.adoc#code-coverage.
I agree it can be useful to find out which functions were never hit.