NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

use Perl

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

Without JavaScript enabled, you might want to use the classic discussion system instead. If you login, you can remember this preference.

Just my topic! :-) (Score:1)

by jk2addict (4946)

I assume you've seen my posts about testing crap that goes wrong at $work?

http://use.perl.org/~jk2addict/journal/31406 [perl.org]

Unfortunately, most of the code is larger than would fit on a slide easily. The image tests are just -e $filename tests...the dup check is just a SELECT NAME, COUNT(*) AS TOTAL WHERE TOTAL > 1 kind of thing...the web page tests wouldn't make much sense outside of context...

The excel import one might be interesting enough.
See my Test::* modules (Score:1)

by nik (3476)

This is why I wrote Test::Net::Connect, Test::Symlink, Test::Unix::Group, and Test::Unix::User (http://search.cpan.org/~NIKC/ [cpan.org]). All designed to test the environment in which code will be running, rather than the code itself.