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
an endless discussion thread about what features to include.
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Universal problem (Score:1)
Any test where you can achieve a perfect score on a subjective metric is destined to cause "not my fault" failures in the future.
For my Test::Virtual::Filesystem [cpan.org] package, I introduced a feature where users could declare themselves compliant with a particular version of the test module. Then, I carefully increment the version of each test in the package when I make a new release, and if the test version number is greater than the claimed compliant version number then I make it a TODO test.
That approach works great for validating POSIX-like filesystems where correctness is quite objective. That approach would probably work for Test::Pod and would partially work for Perl::Critic (make new policies TODO failures == easy; deciding which changes to existing policies should be TODO vs. real failures == hard)
Reply to This