I noticed that some struggle finding a good TDD workflow, in Clojure, with a 
rapid feedback cycle because of the JVM startup time. Especially the people 
comming from RSpec.

So I wrote down my workflow, that is based on speclj, which supports auotesting 
and the typical "describe" "it" "should" way of describing things.
When using the autotesting feature, it keeps a JVM running, this way test run 
with only milliseconds of overhead.

http://velrok.github.io/blog/2013/10/20/test-driven-development-tdd-with-clojure/

All the best,
Waldemar

-- 
-- 
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/groups/opt_out.

Reply via email to