Beefy Boxes and Bandwidth Generously Provided by pair Networks
more useful options

Re: Starting a Large Project

by MAXOMENOS (Scribe)
on Feb 12, 2002 at 02:29 UTC ( #144764=note: print w/ replies, xml ) Need Help??

in reply to Starting a Large Project

I can't add substantially to the material posted here, so I'll add a nit instead.

After you know what a piece of code should do, and before you implement that piece of code, you should write a unit test for that piece of code. This is just so you can be sure that your component works properly, before you go on to build bigger and badder things.

The more crap your unit test does to your component, the better off you will be. Test basic functionality, test weird cases, do stress-tests, throw bad data at it, etc. Learn how your components behave, improve them, and get your component as good as you can possibly get it. It might not hurt to throw in a couple of performance tests, either.

I've gotten bitten by not doing proper unit testing. On the other hand, I once managed to turn my reputation around from 'incompitent' to 'damn, he just saved the contract' by doing proper unit testing.

Just two cents, and sorry I don't got more.

Comment on Re: Starting a Large Project
Replies are listed 'Best First'.
Re: Re: Starting a Large Project
by ignatz (Vicar) on Feb 12, 2002 at 16:20 UTC

    I used to just scoff testing off till the end but now I'm a total test junky. It saves SO MUCH TIME.

    ADDED: Chromatic's article on is a great introduction.


Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://144764]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others romping around the Monastery: (2)
As of 2015-11-28 09:49 GMT
Find Nodes?
    Voting Booth?

    What would be the most significant thing to happen if a rope (or wire) tied the Earth and the Moon together?

    Results (741 votes), past polls