Re: What is wrong with testing like a noob

Some of the benefits of using such standard testing frameworks include:

Being able to run a full automatic suite of tests by kicking off a single command.
Being able to summarize the infomration from those tests easily, and see what if any actual issues there are.
Being able to easily allow other people to test your code, again, just by running a command. This is the easiest way to get your code tested on other platforms.
By using common tools, your stuff is going to be easier to be quickly understood by others.
Any body else?

Do I lose grammar points for too much use of the passive voice, there? I've always thought that was crap, anyway.

------------
:Wq
Not an editor command: Wq
[download]

Comment on Re: What is wrong with testing like a noob Download Code

Replies are listed 'Best First'.
Re^2: What is wrong with testing like a noob by Art_XIV (Hermit) on Jun 28, 2004 at 14:42 UTC
Dittos to etcshadow, but I'd like to add my two pfenning... There is nothing WRONG with 'testing like a noob', but testing via the Test:: series of modules can make your testing much more thorough and comprehensive. In my opinion, the biggest benefit of a nice suite of unit tests doesn't come during the development of a module or class, but afterwards. Having an easy-to-run set of tests that covers your code shields you from a lot of buggy side-effects that can be created when you are making changes after the initial development. Hanlon's Razor - "Never attribute to malice that which can be adequately explained by stupidity"	[reply]

Replies are listed 'Best First'.

Re^2: What is wrong with testing like a noob
by Art_XIV (Hermit) on Jun 28, 2004 at 14:42 UTC

Dittos to etcshadow, but I'd like to add my two pfenning...

There is nothing WRONG with 'testing like a noob', but testing via the Test:: series of modules can make your testing much more thorough and comprehensive.

In my opinion, the biggest benefit of a nice suite of unit tests doesn't come during the development of a module or class, but afterwards. Having an easy-to-run set of tests that covers your code shields you from a lot of buggy side-effects that can be created when you are making changes after the initial development.

Hanlon's Razor - "Never attribute to malice that which can be adequately explained by stupidity"

[reply]