Right now, there are 25 pending patches (wow! thanks, everyone!)
I don't think I've stressed automated testing enough around here. I
also don't think it helped that 20 Minute Wiki was not test driven.
That was partly a tradeoff to show off a range of things in a short
period of time. You can bet that there are more screencasts coming
that will be test driven.
I also don't think I stressed it enough in the contributing doc, which
is something I'll change.
Here's the short of it: if you send me a patch with unit tests it is
likely to get accepted and put in more quickly. Unit tests let me see
exactly what your code is trying to do and, when I apply the patch,
helps confirm that it does so without breaking other things.
The suite of tests that we have have been invaluable during 0.9
development, because they've helped me make changes without breaking
existing functionality.
They're easy to run ("nosetests"), and pretty easy to write. If you've
got something that you're having a hard time testing, feel free to ask
on the list. Most of this stuff is not *too* hard to test.
Kevin
--
Kevin Dangoor
Author of the Zesty News RSS newsreader
email: [EMAIL PROTECTED]
company: http://www.BlazingThings.com
blog: http://www.BlueSkyOnMars.com
