This seems cool, my approach isn't nearly as sophisticated and much more editor dependent. I've using prelude, which include projectile, which binds C-c p P to projectile-test-project.
There were a couple customizations I had to make to get it really streamlined, though. The command shows up in the compile prompt, but I can get rid of that by customizing compilation-read-command to nil. It doesn't save when this variable is nil, so I bound a keyboard macro to F6: [?\s-p ?S ?\s-p ?P] On Saturday, September 27, 2014 5:43:05 PM UTC-4, suvash wrote: > > Hi friends, > > I have just posted a guide to setup a test driven workflow for Clojure, > the idea being able to have a workflow where one does not have to leave the > editor to execute tests as the files are modified. > It is posted at http://suva.sh/2014/10/27/test-workflow-setup-for-clojure/ > > I hope this comes of use to somebody else as well, as I've been quite > bummed to not have run into a tutorial as such. > > Please feel free to discuss it at reddit / HN as you will. > https://news.ycombinator.com/item?id=8377951 > > http://www.reddit.com/r/Clojure/comments/2hn8u2/a_guide_to_setup_test_driven_workflow_for_clojure/ > > Thanks > #suvash > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to [email protected] Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to [email protected] 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
