Continuous integration servers like Jenkins and CircleCI can display summaries of test results, surfacing information like "which of our tests are slow?" and, crucially, "which of our tests are failing?", without forcing developers to spelunk through the logs.
These summaries are produced by parsing test output, the de-facto standard for which is the JUnit XML format. Although its origins lie in the Java ecosystem, this format can be produced by plugins for many test runners in a variety of languages. For Clojure projects, there is a Leiningen plugin called test2junit.
After setting up test2junit on CircleCI, we ran into an issue with all failures being reported to come from line 153 of junit.clj, rather than the actual location in our test code. We also discovered that the context added in 'testing' blocks is omitted from the test summary, so decided to roll our own plugin to improve the output and make it easier to identify and diagnose test failures.
and add the plugin to project.clj:
:plugins [[lein-test-report-junit-xml "0.2.0"]]
Now you can sit back and enjoy your detailed test failures.
On second thought… maybe you should go and fix them…