Clojurians Log v2

interesting use case @charliebriggs, I guess most people don't use the output capturing that deliberately, it's more a "since this code happened to generate some output maybe you should see it when the test fails." We could add an option to have the output buffer reset for each testing context. Would you mind making a ticket on Github just to track this? if you or anyone else in interested in trying to implement this I'd be happy to give some pointers and help you get started.

I find myself getting a handful of errors, say 4 or 5, but with 200-line stack traces. I want to see the stacks so I can figure out what's wrong, but I'm also finding it tedious to page up a dozen times or more to find the topmost failure of the most recent run.

has there been any thought given to a web reporter or other more navigable form of output?

Sure, I've raised this: https://github.com/lambdaisland/kaocha/issues/164, thanks for the response