Not a substitute for proper benchmarking, I know, but could still be directionally useful for answering the “which test is slowing down my feedback loop” question quickly

@UHJH8MG6S we had something like this, didn't we? I don't remember if it was proprietary code

probably it was a very simple :each fixture which I would painstakingly remember to add to every ns. Not fancy, but it will work in every test runner - I like clojure.test as an interoperable standard :)

We have switched most internal projects to kaocha with junit reporting. Which does include this info i think. Our CI can then determine slowest tests and suites over time 😁

kaocha does this, yeah

It may bit be that hard to make one, I can try to hack something later if you want :)

Kaocha has a built in profiling plugin that does this