Author of lein-test-refresh <https://github.com/jakemcc/lein-test-refresh> here! I’m glad you’re loving it. Thanks for sharing that. It feels great to know others are finding it useful.
A couple tips that are somewhat buried in the projects readme <https://github.com/jakemcc/lein-test-refresh/blob/master/README.md> and various blog posts (1 <http://jakemccrary.com/blog/2015/04/25/quieter-clojure-dot-test-output/>, 2 <http://jakemccrary.com/blog/2015/12/18/even-quicker-feedback-from-your-clojure-tests/>, 3 <http://jakemccrary.com/blog/2014/02/02/flexible-notification-of-clojure-tests-failing/]> ). 1. You can have another command run whenever your tests finish running. docs <https://github.com/jakemcc/lein-test-refresh/blob/master/README.md#notifications> 2. You can suppress clojure.test’s *Testing namespace* output. docs <https://github.com/jakemcc/lein-test-refresh/blob/master/README.md#reduced-terminal-output> 3. You can get even quicker feedback by only running tests in namespaces that needed to be reloaded. docs <https://github.com/jakemcc/lein-test-refresh/blob/master/README.md#only-run-changes-in-changed-namespaces> 4. If you hit Enter in the terminal running lein test-refresh all your tests will run. Useful for if you are taking advantage of above or if you have some external state that doesn’t cause tests to reload and run. You can configure these settings by adding configuration values to your project.clj or profiles.clj. Below is my setup which uses OS X’s built in notifications (by sending test result to terminal-notifier), suppresses some of clojure.test’s noise, and only runs tests in changed namespaces. :test-refresh {:notify-command ["terminal-notifier" "-title" "Tests" "-message"] :quiet true :changes-only true} Glad you’re enjoying it. I dread going back to a language where I can’t have a tool like this. Jake On Sunday, May 22, 2016 at 2:58:50 PM UTC-5, Alan Thompson wrote: > > I just discovered this today by accident, and I am loving it! > > When I run tests for the Tupelo library > <https://github.com/cloojure/tupelo>, it requires 8.5 sec to do "lein > test". This seems to be mostly compiling Clojure itself, since JVM startup > takes only 0.038 sec. > > Using "lein test-refresh" in another window, every time I save a change to > the source code it reloads every source file and re-runs every test. The > best part is that all of this takes only 0.4 seconds (more than 20x > faster), and is complete before I can even take my eyes from the editor > over to the test window. > > Very nice stuff! > Alan > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
