Timur writes: > Hi all, > > I'm using Clojure to build a set of services. > > Development with Clojure is fun but most of the time, I lose time with > fixing regressions due to changing small parts of the codes. Do you > have any best practices to avoid regressions occurring due to changes > in the code? I use :pre and :post conditions. Sometimes, they are not > sufficient. do not write so far regression tests as they are quite > time consuming. Writing these tests will be probably an answer, I > guess. Do you have any guidelines to write good regression tests? It > would be nice if I could re-use the code that I type into the REPL to > test separate functions, into the test code but most of the time it > somehow does not work. Another problem I'm facing is many functions > are dependent on each other, so I cannot test each separately, I pass > the results in a map and each function updates the map, so I cannot > write really atomic tests. > > Any suggestions?
Typed Clojure maybe? /M -- Magnus Therning OpenPGP: 0xAB4DFBA4 email: mag...@therning.org jabber: mag...@therning.org twitter: magthe http://therning.org/magnus Eagles may soar, but weasels don't get sucked into jet engines. -- 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.
