Thank you all for the great suggestions I'll start using some of these libraries.
I tried now again with cider and found out what I needed to do. Apparently if I change any file I have to first do a M-x cider-refresh and then running the tests will reflect the situation. Can that not be automated for every save file? Could be a simple hook on save file that calls that, isn't there something like this already? 2015-01-09 5:21 GMT+00:00 Dave Della Costa <ddellaco...@gmail.com>: > One more suggestion as you mentioned wanting to see more output, > although this may be different from what you were asking--but still > worth knowing about: > > https://github.com/pjstadig/humane-test-output > > Cheers, > > DD > > On 2015/01/08 20:30, andrea crotti wrote: >> Hi guys, >> >> I'm starting to use Clojure a bit more seriously, I knew already Lisp a >> bit and Haskell, in plus I've been using Emacs for a long time so >> luckily it's not as hard, and it's a lot of fun. >> >> I'm using Emacs + Cider for development and it works wonderfully, >> however I have a few problems/questions trying to do TDD. >> >> 1. Isn't it possible to make Lein more verbose? >> >> It's often quite slow and it would be nice to know what is going >> on, I can stand the slowness but at least tell me something :D >> >> 2. When is exactly that I need to run again "lein test" (which is >> painfully slow) and when just rerunning the tests from the same REPL >> suffice? >> >> I thought only when changing dependencies, but I had different >> experiences so I'm not too sure about the rule. >> >> And what command exactly is Cider triggering when I run the tests? >> It would be nice to be able to see somewhere more information like: >> - compiling file x >> - running tests for y with command z >> >> 3. Does incremental compilation work well/make sense for Clojure? >> I found something but the fact that it's not done straight away in >> Leiningen makes me think it's maybe not much used? >> >> Thanks a lot, and congratulations to all the developers for the great >> language! >> > > -- > 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. -- 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.
