Hi, It means Test Driven Development. It defines the process of writing the unit test before writing the "real code". The steps are roughly: 1. write a test for a feature you want. For example, "when I add a Movie instance to an empty Movies collection, then Movies size should increase by one" 2. check your test fails (in most cases) as you still haven't implement your feature 3. write the real code (the simplest that should make your test pass) 4. check your test pass 5. refactor both real code and test code, generally searching for code duplication.
This enables that: - most of your code and cases is tested - simpler code - confidence in your code - quicker development as you immediately know when something breaks, thus less debugging. A book I've learned a lot from is Dave Astels's Test Driven Development: A practical guide. Laurent Laffont On Fri, Jun 19, 2009 at 8:58 AM, Alain Plantec <[email protected]>wrote: > sorry but what is the meaning of "TDD" ? > Alain > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
