I've written a lot of tests using Clojure's with-test, which is slightly less elegant, but the same style: https://clojuredocs.org/clojure.test/with-test https

I've written a lot of tests using Clojure's with-test, which is slightly less elegant, but the same style: https://clojuredocs.org/clojure.test/with-test https://clojuredocs.org/clojure.test/with-test I've found it wonderful and productive for low-level bits of functionality, especially working on small data structures and primitives. With Emacs set up to reload the namespace and run all the tests on every save, it's a great feedback look with very little cognitive overhead. It breaks down a bit for more involved tests, as you say, and it can be taxing knowing when to refactor, how much test setup code to include along with the unit under test, and also once you start splitting things into other namespaces, where to look to get a full view of a module's functionality.