Using Perl Test Capabilites - When Not Writing Modules?

jonasbn on 2002-10-04T11:18:19

Today I had a 'YAPE' *1. I have written a small CGI script using Perl. It is not a module - it is a simple script, which suites a single purpose, but uses a lot of existing Perl (CPAN) modules. So in order to provide this script with some accompanying tests - I thought what the heck, I'll simply write a test.pl which test that the prerequisites are in order now when I do not have a makefile, cause having a makefile for a CGI seems somewhat stupid.

And since testing is (as I always say), a - SAMP *2, heh I stole this term from an IBM consultant, but I don't think he will mind, and I am not sure whether it is correct but you get my meaning.

So now my CGI script is accompanied by a test.pl and a t directory, which makes in intuitionally easier to test and with more tests I feel confident in the stuff I am programming, but that is another story, bottomline is: Test! it is fun and it is just plain ol'e programming :)

*1 Yet Another Phantastic perl Experience, Perl is intentionally written with a lowercase P.

*2 Simply A Matter of Programming


SAMP

vsergu on 2002-10-04T12:53:54

I think the usual term is "SMOP".

Re:SAMP

jonasbn on 2002-10-05T07:26:24

That is it 'SMOP' and not 'SAMP'. It also sounds more british that SAMP, the IBM guy I heard use it was british, so it sounds just right.

Thank You...