I’m not aware of anything that serves that need for clojure.test but if I had to solve it, I’d wrap the deftest macro in something that records runtimes in e.g. a map in an atom indexed by name.

@aaron51 it depends a bit on the context. For example on CI, you could use test2junit to run your tests, which will generate junit xml reports, then you could use a script to extract that information. There's an example script here: https://github.com/caarlos0-graveyard/junit-slowest-tests/blob/master/slowest-tests