Now that I am starting to do things on my own instead of on a team, I am having to test my own software. Well, I am used to having someone test mine and me test theirs. Since that is no longer an option, can anyone suggest methods, ideas, or perl-based QA tools that will help me make sure the code that leaves my doors is the best it can be.


I admit it, I am Paco.

Replies are listed 'Best First'.
Re: Quality Assurance
by lachoy (Parson) on Feb 06, 2002 at 20:51 UTC
Re: Quality Assurance
by Moonie (Friar) on Feb 06, 2002 at 18:18 UTC
Re: Quality Assurance
by cjf (Parson) on Feb 06, 2002 at 20:48 UTC
    While I'm tempted to suggest posting all the code online, I realize this is not always possible (although you should still bring up the issue of Open Source and its benefits with your employer :). If you are required to keep the source closed, pay extra attention to security. I also recommend trying to break your code, throw everything at it and see how it holds up, if nothing else it sure is fun :)