On Nov 29, 12:35 am, Fuzzyman <[EMAIL PROTECTED]> wrote: > Your experiences are one of the reasons that writing the tests *first* > can be so helpful. You think about the *behaviour* you want from your > units and you test for that behaviour - *then* you write the code > until the tests pass.
Thank you Michael, you are perfectly right in reminding me this. At this particular point in time I'm not yet architecturally foresighted enough to be able to do that. While I was writing the design documents I did write the list of methods each object would have needed and from that description theoretically I could have made the tests first. In practice, while eventually writing the code for those methods, I've come to realize that there was a large amount of variance between what I -thought- I needed and what I -actually- needed. So, had I written the test before, I would have had to rewrite them again. That been said, I agree that writing the tests before must be my goal. I hope that as my experience increases I'll be able to know beforehand the behaviors I need from each method/object/module of my applications. One step at the time I'll get there... =) Manu -- http://mail.python.org/mailman/listinfo/python-list
