Ed Leafe wrote: > On Jan 15, 2007, at 12:52 PM, Paul McNett wrote: > >>> Unit tests are like compiler type checking: the fact that you passed >>> doesn't mean the code will work. >> And the current unit tests only test MySQL and SQLite, and don't fully >> cover every method, property, or use case in the classes yet. Units >> get >> tested for expected output, which is a valuable thing to have, but we >> still need to rely on real-world testing as well. > > That's exactly what I meant. They serve a valuable purpose, but they > are not proof of anything beyond what they specifically tested.
As we move on, and more people get more involved with Dabo's development, I hope to have the unit tests filled out to a point where if someone wants to change behavior or add new features, the very first step will be writing the suite of tests to check the expected outputs. Only after the tests are written will the code in the classes be changed/added. And only after all the tests pass will the new code be committed. -- pkm ~ http://paulmcnett.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
