cloverage

https://github.com/lshift/cloverage/issues/103
2017-07-11T00:22:01.573779Z

So I’m having a little bit of trouble with cloverage and schema

2017-07-11T00:22:20.577886Z

I want to use cloverage to see where I have large amounts of untested code, so I can test it

2017-07-11T00:22:31.580095Z

but if I look for a file with lots of untested forms

2017-07-11T00:22:54.584973Z

a lot of times those forms are coming from some macro and I don’t really care if they get tested

2017-07-11T00:23:24.591033Z

like, I have a bunch of functions defined with schema.core/defn and every one of them has schema validation and error reporting code inlined into it

2017-07-11T00:24:01.598749Z

similar problem is when doseq and for produce two branches — one for a chunked sequence, one for unchunked, and I don’t actually care which one was taken

2017-07-11T00:24:45.607407Z

The trouble is that at this point my code is tested decently well, and so when I go looking for untested code, most of it is stuff like this that I don’t care about

2017-07-11T00:25:01.610724Z

and if I could get this stuff to stop showing up, I’d have an easier time finding the remaining untested code

2017-07-11T00:25:47.620455Z

and I’m wondering if there are ways to annotate things or provide compile-time flags or something so that this extraneous code doesn’t complicate things

2017-07-11T00:26:19.627275Z

I mean, I can see some ways forward but I’m wondering if this is a problem someone has already had and done something about

2017-07-11T19:50:53.381225Z

oh, never mind, that was easy https://github.com/plumatic/schema/blob/master/src/clj/schema/macros.clj#L181