After many years of writing Perl I am finally starting to write tests for the modules that I've written, and this is presenting me with a bit of a challenge.
My first test file starts with .. shall we say .. a base object, from which all other objects flow. My plan is to be able to run this test right after an install to check that some bare bones functionality is present, and again after I've primed the system with a few test files.
Thus, the second test run will be more comprehensive. I believe I know how to do that, using Schwern's excellent Test::More and the SKIP: feature, but I'm concerned that I'm going to end up with a larger and larger test file. Should I, or can I, break out the other tests into separate files in an attempt to modularize? Or is there a cunning way to run groups of tests from a superior file?
I welcome your feedback.
Alex / talexb / Toronto
"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds
In reply to How to structure tests that span several modules by talexb
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |