Keep It Simple, Stupid | |
PerlMonks |
Re: Testing Non-module codeby whiteEFunk (Acolyte) |
on Mar 16, 2004 at 18:46 UTC ( [id://337084]=note: print w/replies, xml ) | Need Help?? |
I found that writing tests along with the code helps me catch error conditions early. I use Test::More. Sometimes, the code I write is not intended to run in my development/test environment. In these cases I modify package objects, or data structures within the tests to get the desired scenario. Then I run a test against it. Test::More example: foo.pl contains a function named foo_plus_one like this - You can 'require' your script into the test - and call the functions -
pass output - 1..1 ok 1 - method foo_plus_one() OR fail - 1..1 not ok 1 - method foo_plus_one() # Failed test (foo.t at line 6) # got: '1003' # expected: '5' Testing is a great way to build a program! Ye-haw!
In Section
Seekers of Perl Wisdom
|
|