I would be so excited about this. Most folks probably don't remember that it was actually quite controversial for the first workshop -- half of us felt we should teach TDD and half felt testing was an advanced topic. For the first workshops, each teacher taught from a basic outline and did whatever they felt was right.
When I flew out to Boston for the workshop at Harvard in the fall, where there would be 50 students per teacher, I wrote up all of the detailed steps of the app which became the basis of the first curriculum. About a year later Yehuda Katz advocated for TDD once again, and helped create a cucumber-based curriculum. A couple of years later, I think it was Seattle moved away from TDD, but I'm not sure whether it was really anti-TDD and more that it presented the concepts separately from the step-by-step, which everyone really liked.
There's been a lot of discussion in the Ruby community about whether testing should be taught in intro classes, or whether it is an advanced topic. I feel like it is helpful for complete beginners to do stuff interactively at first, but if you don't teach them testing pretty early on, you are doing them a disservice. When I taught professionally, I developed a pattern of:
1) introduce concepts (basic syntax, patterns and why they are learning this)
2) interactive programming to give them a feel for it (usually with irb)
3) Test first teaching (give them a failing test, they write the code to make it pass)
My test first teaching was inspired by Alex Chafee who had used this technique to teach Java. I made the Ruby lessons, and later I contributed the JavaScript lessons (if I recall correctly, based on those that were taught at Blazing Cloud).
It's officially a project of Bridge Foundry. I also have Rails lessons that I never added and would be happy to share. Also, there's
2010 GoGaRuCo talk, if you are interested in the TFT pedagogy.
I'd be very excited to see a Bridge curriculum that emphasized testing!
Sarah