Clojurians Log v2

Started going through our Polylith bricks that don't have tests (yes, yes, I know) and spent the afternoon writing LazyTests for them. We used to auto-generate a stub test ns for every source file, which just required the source ns as a sanity test, but we do a full compile looking for reflection/auto-boxing warnings now instead, so we deleted all the "empty" test nses and I'm slowly putting actual tests back into those holes. We do TDD for some stuff and we write unit and integration tests for some stuff, but a lot of CRUD-like code at work has no tests... so I'm slowly teasing that apart and writing new tests 🙂 for any of the business logic stuff (as opposed to raw CRUD).

how does the lazytest api feel? any warts or places of discomfort?

It's working pretty well for me so far. I tend to have a hard time coming up with a docstring for defdescribe but test cases via it generally have "obvious" docstrings. I haven't started looking at the matcher combinator stuff yet but that's on my list.