It's still cooking. I just passed 150 NUnit tests. Right now I'm having to veer off into the tools to import and interact somewhat with FitNesse. My team is getting started with FitNesse and I think I'll use the project work a little bit as a testbed for StoryTeller.
I've gotten a couple volunteers to help code and try out StoryTeller.
I'll be sending emails to everybody in the next couple days. If you
want to jump on board, the easiest thing to do might be to go request a
role at http://storyteller.tigris.org.
How's this for irritating? We're driving automated acceptance testing of our WinForms application with FitNesse calling through NUnitForms (I'll blog about our experiences in a couple weeks). We're using, or at least trying out, a third party control library for oohs and aahs in the user experience. Great, except for one little problem. Apparently you can only load a single instance of a certain control in any one AppDomain. Since the FitNesse tests work by starting up the main form at the beginning of every test (gotta start clean), only the first test you run will work correctly. Just to beat this without spending months looking at the controls in Reflector, I'm building equivalents to FitServer.exe and TestServer.exe inside StoryTeller that will construct and teardown a new AppDomain for every single test. Grrr. Typical Microsoft world stuff, thousands of man hours spent on Design Time support and very little on testability.
Of course, one of the reasons I enjoy test automation is that the code is generally more challenging than the day to day CRUD.