|
From: Johannes N. <joh...@gm...> - 2006-05-09 08:27:04
|
unit testing was a pain for me in the begining, i hated writing proper tests, always slacked and paid the price for it later. when i got into unit testing full-on i found my life became so much easier when bugs were filled against me. you get a bug, follow the steps to recreate it, notice a new edge case, write it up and voila you have broken tests. also once you have several people working on a project with a proper continues integration system, you find yourself in a world where if any tes= t breaks with checked in code, everybody gets notified. very few things slip underneath the radar like that... i am a lazy sod however so i use automated ways of creating my test shells and the like, i would advice you to do the same. On 5/9/06, Johannes Nel <joh...@gm...> wrote: > > i left it there, consider it a gift from our kind employers... ;) > > > On 5/9/06, Peter Hall <pet...@gm...> wrote: > > > > I just found that Kent Beck book in my apartment! Not sure exactly wher= e > > it came from. Anyway... it looks pretty good! > > > > > > Peter > > > > > > > > On 5/9/06, Luke Bayes <lb...@gm...> wrote: > > > > > > This is a great question! > > > > > > The single best source that I've found is the book, "Test Driven > > > Development by Example" from Kent Beck. > > > > > > This book really cleared up a lot of questions for Ali and I. > > > > > > I also got a lot of inspiration from the Gang of Four Design Patterns > > > book - this book helped me see the underlying (testable) object struc= tures > > > that are behind gui systems... > > > > > > > > > Anyone else? > > > > > > > > > > > > Luke Bayes > > > www.asunit.org > > > > > > > > > > > -- > j:pn > http://www.lennel.org > -- j:pn http://www.lennel.org |