more useful options | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
The reason the tests in examples use the modules is simple: that way, the tests can be in a separate file, and not in the main program file.
The one thing you don't want to do is to be testing a copy of your routines: sooner or later (probably sooner) you would forget to update the testing copy from your current copy, and you would be wondering why the tests aren't affected by the changes you made. Using the same modules from the test program as well as from the program you're developing neatly avoids that. But there is an alternative. You could use Test::Simple (or any of the other test tools) from within the target application itself, probably only when it was called with a specil parameter like --run-tests. When such a parameter was given, you would simply run a testing procedure instead of the regular run procedure. I hope this makes things a bit clearer. Happy testing! In reply to Re: Testing Non-module code
by matija
|
|