pboin has asked for the wisdom of the Perl Monks concerning the following question:
Like many of you folks, I've read PM for a while, and had that nagging 'I can do it better' thing hanging over my head for a while, and now I want to look into writing test cases.
I read some neat articles, and while I haven't tried it yet, I think I get the point about test cases being written and living in the 't' subdirectory.
Problem is, that those cases all seem to 'use' modules, get a new instance and work with it. A lot of my existing code isn't in Modules, it's plain ol' procedural code. Of course, I'm careful in error checking, etc, but how can I incorporate formal ok/'not ok' testing w/o having modules to call?
Oh, and a great big 'Thank You' to all PM folks, new and old!
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: Testing Non-module code
by dragonchild (Archbishop) on Mar 16, 2004 at 13:18 UTC | |
Re: Testing Non-module code
by matija (Priest) on Mar 16, 2004 at 14:14 UTC | |
by paulbort (Hermit) on Mar 16, 2004 at 18:59 UTC | |
by grantm (Parson) on Mar 17, 2004 at 08:39 UTC | |
by pboin (Deacon) on Mar 16, 2004 at 14:23 UTC | |
Re: Testing Non-module code
by whiteEFunk (Acolyte) on Mar 16, 2004 at 18:46 UTC | |
by pboin (Deacon) on Mar 17, 2004 at 11:00 UTC | |
Re: Testing Non-module code
by QM (Parson) on Mar 16, 2004 at 19:50 UTC | |
Re: Testing Non-module code
by eserte (Deacon) on Mar 16, 2004 at 19:23 UTC |