|
|
| Think about Loose Coupling | |
| PerlMonks |
Re: Testing programsby pboin (Deacon) |
| on Oct 25, 2005 at 13:08 UTC ( #502696=note: print w/ replies, xml ) | Need Help?? |
|
This got me for a while too. The way you're doing it seems to be commonly accepted. I think that if you have procedural functions, you can also require it, and then use the test harness against the subroutines. One of the most important concepts I got from the thread was that you definitely do not want to get into testing a copy of your code. That will inevitably lead to problems w/ syncronization (and hassle). Here's a good thread on it: Testing Non-module code
In Section
Seekers of Perl Wisdom
|
|
||||||||||||||||||||