test-runner VS pomegranate

> I had to Grok Integrant again because I wouldn't understand my project otherwise.

You can use plain functions and `reduce` for system composition if you want. Take a look at how Biff does it: https://biffweb.com/p/thinking-about-system-composition/

DI should be used sparingly for the top-level, stateful pieces of your system. If you can't understand your program without it, is this a problem with Clojure itself or the design of the program?

> And when it comes to best practices around unit testing, it's another one of those things where no one in the community seems to be sharing much about it.

The `clojure.test` API has stayed the same for the last decade and that's what you'll see in most projects. Is the concern about how to run tests? Both of the following libraries work well:

Minimal test runner: https://github.com/cognitect-labs/test-runner

:aliases {:test {:extra-paths ["test"] :extra-deps {io.github.cognitect-labs/test-runner {:git/url "https://github.com/cognitect-labs/test-runner.git" :git/sha "8c3f22363d63715de4087b038d79ae0de36a3263"}} :main-opts ["-m" "cognitect.test-runner"] :exec-fn cognitect.test-runner.api/test}}

Cognitect's test-runner is probably the most commonly used approach with deps.edn and the CLI: https://github.com/cognitect-labs/test-runner

https://github.com/clj-commons/pomegranate

However, to do this it uses the same library lein uses for dependency resolution and classpath creation. And of course you can integrate with either deps.edn or project.clj.

You are looking for pomegranate

You can try https://github.com/clj-commons/pomegranate

He mentioned that he's using the add-lib3 branch of tools.deps.alpha to get hot-loading dependencies. If you use lein instead, the pomegranate library enables it.

The only time I need to restart is when I load new libraries but you can use https://github.com/clj-commons/pomegranate