We have a workshop later this month on TDD and we're looking for attendees and experience reports. We already have a couple Ruby programmers attending, so I thought I'd reach out to others here in Indy.
In this workshop we want to look at testing done by the programmer, for the programmer. For this workshop, experience reports would cover topics such as:
- getting started with TDD
- working in legacy code that does not have existing unit tests
- managing large test beds of unit tests
- setting up and managing continuous integration
- designing mocks, stubs, and harnesses
- using unit tests to aid in refactoring
- dealing with team/cultural issues when implementing TDD
- tools that assist with TDD and unit testing
- and non-traditional unit testing (dbunit, xmlunit, etc...)
This workshop could also potentially have an exercise or two where participants write a class using TDD with a series of debriefs/lightning talks of why they used the tests that they did. Problem solving opportunities are very welcome for this workshop.
Dustin Sparks, a local development manager, has volunteered to take on the role of content owner for this workshop. Our hope is that this topic will entice programmers who have a passion for well tested code, who want to share what they've learned, and who want to get better at their testing.
Date: Friday March 27, 2009
Location: Mobius Labs
Time: 8:30 AM - 5:00 PM
Format: All-day workshop
If you're interested, drop me a line. As always, it's all free (you'll have to pay for your own lunch). All we ask is for your time and participation.