: What seems difficult to do in general is to automatically decide
: whether or not a given test result is useful or redundant.
: Suppose distribution A has a standard test suite, plus some
: additional tests depending on if an optional distribution B is
Good point, I hadn't considered the complexities of optional tests based
on other modules installed.
: The tests won't be rerun - the module saves the dialogue from the
: last make, test, or install session done thru the shell to a file,
: which you can then include in the comments section of the report
: by an appropriate switch to the "cpantest" command.
Hmm, it sounds like that could be enough. If shell users know that
they can just run "cpantest" after any install/test and easily submit
their results, it's almost as good as "auto-magically", and it will cut
down on a lot of redundant "PASS" emails.
Excellent.
The only improvement I can think of, would be to inform the user if no
one else has ever submitted results for this Module on their particular
perl/osname/psvers/archname combo. "Eencouraging" them to submit their
results.
--
-------------------------------------------------------------------
"Oh, you're a tricky one." Chris M Hostetter
-- Trisha Weir [EMAIL PROTECTED]
