Clojurians Log v2

I use cider’s support for running tests

As long as you include the :test alias when launching Cider, it should work with cider's built-in test support (`cider-run-project-tests` etc) (in emacs -- https://clojurians.slack.com/archives/C013B7MQHJQ/p1725449800690879 as in this earlier thread!)

Thanks @jasonjckn for confirming it’s a valid workflow and @patrix for flagging you need the test alias. Sounds like the root cause is me not setting up cider correctly. If I may ask, when you run tests do you run them via cider/repl? I’ve found running via cli is best because it’s consistent. When running from cider/repl, get errors that tests don’t exists (can’t find is) if I don’t manually load them which is a pain.

Nothing beats cider for running just a single test , i'll move my cursor to the test i want to run and hit , t t in doom emacs If i'm running the entire test suite i'll use polylith cli, if i'm running a namespace test suite, i'll flip between cider & cli --focus , just whatever happens to be more convenient at the time. Also there's cider-auto-test-mode which i don't enable that by default via cider-mode-hook, but i'll enable that mode sometimes depending on what i'm doing. There's a couple runtime differences between the two, for example, in cider, if you delete the test code, and you rerun the namespace tests, that function is still defined in the REPL environment, so you'll have a 'phantom' unit test with no code, but if you use tools.namespace refresh or clj-reload, that can help with that scenario. You should be able to get both environments to match for the most part. Obviously polylith test is much more exhaustive because it enumerates through every project/ possible classpath, and you can't approximate that in cider.

Right, I also use Doom Emacs so it might be specific to Doom as well that all tests are loaded when including the :test alias