Discussions around TDD / RDD (REPL-Driven-Development) probably need a separate thread but...
On Feb 4, 2014, at 5:17 AM, Mimmo Cosenza <mimmo.cose...@gmail.com> wrote: > thanks for the report. I only have few doubts about REPL making TDD to shame. I'm a strong advocate of TDD (well, BDD specifically) and I agree with Jay's comment insofar as you write a "test" expression in the REPL and it evaluates immediately. That's always faster than writing a test and running a test, by definition. That's all I took his comment to mean. > The REPL is great, that's for sure, but IMHO it does not relegate TDD > feedback/loop in a niche, because you can complement one with the other. Indeed you can - and Jay does - and so do I. Especially now I'm using LightTable and can evaluate code in place in amongst my production code in one tabset and my expectations in another tabset. I have C-c , bound to evaluate a "run-tests" expression in my namespace so I can quickly evaluate and execute tests. Even so, live evaluation of "test code" is still a faster feedback loop. Many of my test expressions become long-lived unit tests (expectations). Or they become production code. I still write expectations to clarify how to design APIs in the small (and APIs in the large as needed), but most of the red-green-refactor loop of TDD/BDD now comes from the REPL experiments for me. Sean Corfield -- (904) 302-SEAN An Architect's View -- http://corfield.org/ "Perfection is the enemy of the good." -- Gustave Flaubert, French realist novelist (1821-1880)
signature.asc
Description: Message signed with OpenPGP using GPGMail
