Re: functional thinking

2010-12-03 Thread ka
Hi Michael, We're in a very similar situation to yours. Here's what we did: 1. 2 back end storage impls rah.storage1, rah.storage2 - these are "private" nses. 2. a single storage interface rah.storage for the rest of the business code. At runtime this decides which of storage1 or 2 to call. 3. No

Re: functional thinking

2010-12-02 Thread Michael Ossareh
On Wed, Dec 1, 2010 at 10:51, Alyssa Kwan wrote: > Hi Mike, > > "TDD as if you meant it" - > > http://gojko.net/2009/02/27/thought-provoking-tdd-exercise-at-the-software-craftsmanship-conference/ > > What you want is mocking and stubbing (these are different things!). > > http://s-expressions.com

Re: functional thinking

2010-12-02 Thread Michael Ossareh
On Wed, Dec 1, 2010 at 05:29, Laurent PETIT wrote: > Hi, > > 2010/12/1 Michael Ossareh > > Hi All, >> >> In the course of putting together my latest piece of work I decided to >> really embrace TDD. This is run of the mill for me in Java: >> >> - create some object that models your flow >> - cre

Re: functional thinking

2010-12-01 Thread trptcolin
On Dec 1, 3:33 pm, Ken Wesson wrote: > On Wed, Dec 1, 2010 at 9:38 AM, Laurent PETIT wrote: > > 2010/12/1 Ken Wesson > > >> On Wed, Dec 1, 2010 at 8:29 AM, Laurent PETIT > >> wrote: > >> > If so, then it may be sufficient to leverage the possibility, in your > >> > testing "framework" (clojure.

Re: functional thinking

2010-12-01 Thread Laurent PETIT
2010/12/1 Ken Wesson > On Wed, Dec 1, 2010 at 9:38 AM, Laurent PETIT > wrote: > > 2010/12/1 Ken Wesson > >> > >> On Wed, Dec 1, 2010 at 8:29 AM, Laurent PETIT > >> wrote: > >> > If so, then it may be sufficient to leverage the possibility, in your > >> > testing "framework" (clojure.test ? any

Re: functional thinking

2010-12-01 Thread Ken Wesson
On Wed, Dec 1, 2010 at 9:38 AM, Laurent PETIT wrote: > 2010/12/1 Ken Wesson >> >> On Wed, Dec 1, 2010 at 8:29 AM, Laurent PETIT >> wrote: >> > If so, then it may be sufficient to leverage the possibility, in your >> > testing "framework" (clojure.test ? anything else ...) to redefine the >> > fu

Re: functional thinking

2010-12-01 Thread Laurent PETIT
Note, though, that he did not use the words "unit testing", you did :) And mocking and stubbing are techniques that can be done at different scales ... 2010/12/1 Alyssa Kwan > Hi Mike, > > "TDD as if you meant it" - > > http://gojko.net/2009/02/27/thought-provoking-tdd-exercise-at-the-software

Re: functional thinking

2010-12-01 Thread Alyssa Kwan
Hi Mike, "TDD as if you meant it" - http://gojko.net/2009/02/27/thought-provoking-tdd-exercise-at-the-software-craftsmanship-conference/ What you want is mocking and stubbing (these are different things!). http://s-expressions.com/2010/01/24/conjure-simple-mocking-and-stubbing-for-clojure-unit-te

Re: functional thinking

2010-12-01 Thread Laurent PETIT
2010/12/1 Ken Wesson > On Wed, Dec 1, 2010 at 8:29 AM, Laurent PETIT > wrote: > > If so, then it may be sufficient to leverage the possibility, in your > > testing "framework" (clojure.test ? anything else ...) to redefine the > > functions of the backend before the tests run. I'm pretty sure th

Re: functional thinking

2010-12-01 Thread Ken Wesson
On Wed, Dec 1, 2010 at 8:29 AM, Laurent PETIT wrote: > If so, then it may be sufficient to leverage the possibility, in your > testing "framework" (clojure.test ? anything else ...) to redefine the > functions of the backend before the tests run. I'm pretty sure there are > already such features a

Re: functional thinking

2010-12-01 Thread Laurent PETIT
Hi, 2010/12/1 Michael Ossareh > Hi All, > > In the course of putting together my latest piece of work I decided to > really embrace TDD. This is run of the mill for me in Java: > > - create some object that models your flow > - create some object which contains your storage logic > - create test

functional thinking

2010-12-01 Thread Michael Ossareh
Hi All, In the course of putting together my latest piece of work I decided to really embrace TDD. This is run of the mill for me in Java: - create some object that models your flow - create some object which contains your storage logic - create tests - dependency inject the correct storage logic