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

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.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Everyone works on different projects, so it's hard when people like Schwern and Andy say "just start testing your code!" to know what aspects of your code to start with. Baby steps, training wheels ... that'd be good.

    I have started implementing core tests that every module is expected to call - stuff like 01compile.t, 02import.t, 03constructor.t, and so on. the idea is that every module should be testing pretty much the same thing at the outset. and even if there is no need for an import() test, I expect the file to exist and print a skip message, just so everything is uniform to a certain part. I have personally found that dictating a few simple things like that help to get people to start thinking in "test."