Ah, now that's a good idea - we can also make some good educated gueses about this too. We have the last version of the TurboPower Sleuth QA product that I think has a tool for doing that.
The point about writing tests for existing code as you write it also appeals - more than half our work is modifying existing code so this too would cover a lot of important areas. Cheers, Nahum > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > [EMAIL PROTECTED] > Sent: Friday, 17 June 2005 11:46 a.m. > To: [email protected] > Subject: RE: [DUG] RE: Unit Testing > > > 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. > > You may want to run a code coverage tool (AQTime can do it) > to see what areas of your system gets hit the most during a > "typical" run of your application and look at those areas to > create unit tests for first. > _______________________________________________ > Delphi mailing list > [email protected] > http://ns3.123.co.nz/mailman/listinfo/delphi > _______________________________________________ Delphi mailing list [email protected] http://ns3.123.co.nz/mailman/listinfo/delphi
