Shawn Sorichetti wrote:
It occurs to me that the Test::* and ExtUtils::* modules should be the first stop for the Phalanx project. :)Test::Output 0.05 has been released.
The main difference in this version is a patch from chromatic (thank you). His patch fixed a bug where all tests printed error diags even if they passed. Additional tests were added to ensure that no output is sent from diag in successful tests.
While releasing this version I realized I never wrote anything about version 0.04 which saw some major changes:
Added fuctions: output_like and output_unlike.
stdout_from, stderr_from, and output_from were removed from @EXPORT and moved to @EXPORT_OK as suggested by Schwern.
Renamed test "comment" to "description".
Refactoring and additional tests.
--- Shawn Sorichetti
Incidentally, is it acceptable for an author to Phalanx-review his own module, or does that defeat the peer-reviewed-ness of it? I'm about to upload my first module, and if Phalanx has some kind of check list that must be satisfied to have the Phalanx-approval-seal (is there one?), then I'd be happy to go through it.
Random thought: Could Devel::Cover be automatically run against all modules in CPAN, with ratings posted on cpan.org right next to the usual test results?
-ofer
