JUnit

[Glen Daniels <gd...@macromedia.com>]

Over the past week, there have been several fixes to restore things that
were working at one point, and then got broken in amidst other changes that
were going on.  Regression tests would have caught this stuff at the point
where it broke, instead of weeks later.

Enter JUnit.  This is something we've talked about for a long time, but now
that we're (hopefully) embarking upon a serious collaboarative development
phase, having testing in the framework is going to be critical.

I'd like to see us fairly quickly move to a world in which every time you
check in a new component, you also include tests, and integrate those tests
into the standard regression which gets run automatically via "ant tests" or
somesuch.  Then if you break something, or if integration breaks your new
stuff, we'll have a clue right away.

This is a little more work up-front, but it pays for itself a hundred times
over in future headaches saved.  Really.

Any volunteers to start working on this?  The two places I see this going
right now are a) integrating JUnit into the build/framework, and b) starting
to design tests for the system....

Glen Daniels
Macromedia
Engineering Manager
http://www.macromedia.com/
                                Building cool stuff for web developers