[OKC JUG] Idea for second Coding Dojo

[Brett L. Schuchert]

While I know the first dojo is still a day away, I wanted to throw out  
another idea for a forth-coming coding dojo (or half-day course):
Taking a mockist (http://www.martinfowler.com/articles/mocksArentStubs.html#ClassicalAndMockistTesting 
) approach to developing a solution.

Beginning with nothing, create a solution from the ground up using a  
mocking library. At any given point, a system under test is the only  
real thing begin tested, all other moving parts are created using test  
doubles either created by hand or via  mocking library (it's be  
Mockito for Java and Moq for C#).

While I do not do this in practice, I use mocking libraries to augment  
development, often hand-rolling test doubles, learning how to start  
from scratch using a mocking library is a good experience, I believe.  
It also feels quite different (mentally anyway) from standard TDD.

Are you interested in this? If you are, please respond. If there are  
few or no responses, then I'll shelve the idea.

If it's a dojo, it's about 2 hours and working one pair at a time. If  
it's a class, it'll be however may people are interested working, some  
working in paris, some not. In any case, it is language/library  
specific, so no mixing, for example, C# and Java at the same time. I  
could do it I suppose but I think it's too confusing from a teaching  
standpoint.

Brett

p.s. While I could use the example (http://schuchert.wikispaces.com/Mockito.LoginServiceExample 
) I blogged about, I would instead use a more interesting (fun?)  
problem for that.