As a programmer, i always test what I'm coding as i code it (mostly to
make sure i dont include typos), but i feel it is best to make proper
testing once the component is ready and working fine. If your project
is large, it might be a good idea to break it in several 'modules' or
section if possible and treat each of them as separate projects
(testing would be done on a module once this one is ready).
You may be interested in looking for information on the net on 'IT
project management' which usually describe when is the best time to
test according to a certain structure...
On Mon, Apr 27, 2009 at 12:16 PM, Nathan Rixham <nrix...@gmail.com> wrote:
> Philip Thompson wrote:
>> Hi. I did some searching in the archives, but didn't quite find what I was
>> looking for. Maybe a few of you can assist me...
>> We have an application that's currently in production, but we're
>> constantly modifying/upgrading it. We did not do unit testing early on
>> because of the lack of time. Now that some time has opened up, we're
>> considering unit testing. My question is..... is it reasonable to start unit
>> testing at this point in time with the application mostly built? Besides
>> being really time-consuming, what are the pitfalls of starting unit testing
>> at this stage?
>> Thanks in advance,
> maybe a useless answer, but, no pitfalls - just do it - I'm always surprised
> by my unit test results, its invaluable and it's never too late to start.
> just think about the next years worth of bugs found by the client not being
> PHP General Mailing List (http://www.php.net/)
> To unsubscribe, visit: http://www.php.net/unsub.php
When Earth was the only inhabited planet in the Galaxy, it was a
primitive place, militarily speaking. The only weapon they had ever
invented worth mentioning was a crude and inefficient nuclear-reaction
bomb for which they had not even developed the logical defense. -
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php