Adi and I came up with a new idea that helps people to focus on small steps and also opens them up for committing small chunks very often. The main idea is that people get a very short time box to write a new test and implement it the simplest way possible. After that they get another short time box to refactor the code.

Here you can find the details of the session

Views: 196

Comment by corey haines on February 4, 2012 at 12:26pm

I've written a quick timer that pairs can use. https://gist.github.com/1736615

It is rudimentary, but should get the job done.

Comment by corey haines on February 12, 2012 at 1:25pm

I've now done this twice, and I love it. The emphasis on small tests really puts a different spin on things.

One thing people have mentioned is that they feel like they are writing small, structural tests, instead of focusing on behavioral tests. This leads to a more test-first approach, verifying an already thought design. This is true for the people I've seen who are less experienced with full-blown tdd. I have seen it do interesting things with more experience people. I'd love to hear thoughts about different things to stress for this exercise based on the level of experience with test-first and test-driven modes.

Comment

You need to be a member of Coderetreat to add comments!

Join Coderetreat

© 2014   Created by corey haines.

Badges  |  Report an Issue  |  Terms of Service