[DUG] RE: Unit Testing

[Allan, Samuel]

This seems like it might be a sensible way to approach this. Because
most of the value of unit tests is easily re-testing something when you
change it to make sure that it is still good. If you write unit tests as
you change code then all the most volatile code will quickly get unit
tests, and the most volatile code is where you can expect to get the
most benefit.

I might be tempted to also extend this to code that you haven't changed,
but are going to manually re-test because of a change elsewhere.

Samuel

-----Original Message-----
From: delphi-bounces at ns3.123.co.nz [mailto:delphi-bounces at ns3.123.co.nz]
On Behalf Of JeremyN at frontiersoftware.com.au
Sent: Friday, June 17 2005 11:30 a.m.
To: delphi at ns3.123.co.nz
Subject: RE: [DUG] RE: Unit Testing


Going back over existing code and writing unit tests for it would suck.
If you modify some existing code, perhaps write a unit test for it then
(if
it is appropriate).

With the new code, look at writing unit tests. 

-----Original Message-----
From: Nahum.Wild [mailto:Nahum.Wild at payglobal.com] 
Sent: 17 June 2005 9:16 AM
To: 'NZ Borland Developers Group - Delphi List'
Subject: RE: [DUG] RE: Unit Testing


Leigh,

I was reading back thru this thread as I initially missed it - it's of
interest to us as we don't do this but we would like to be.  Currently
we
have over 60mb of delphi code without any unit tests - we are trying to
figure out where to start, maybe figuring on only writing tests for new
code
and leave the existing code along.
_______________________________________________
Delphi mailing list
Delphi at ns3.123.co.nz
http://ns3.123.co.nz/mailman/listinfo/delphi