in reply to RFC: Perl Testing -- How to Introduce to a team
If you're testing already-written code, I'd do it top-down, testing overall results first, then working to more granular levels. If you're writing new code, I'd do it bottom-up, module-by-module, function-by-function.
Here are some posts that I've bookmarked that you might find useful:
-xdg
Code written by xdg and posted on PerlMonks is public domain. It is provided as is with no warranties, express or implied, of any kind. Posted code may not have been tested. Use of posted code is at your own risk.
|
|---|