On Fri, 2005-02-18 at 09:25 -0500, Geoffrey Young wrote: > yeah, I'll second this, at least so far as adding a version component to > Test::More goes (which is different than adding a TAP version, which I don't > have an opinion on:). Test.pm currently prints out > > # Using Test.pm version 1.24 > > and Apache-Test follows suit with > > # Using Apache/Test.pm version 1.16 > > and I always wished that Test::More and friends would follow suit. for > instance, it might help if someone reports test failures and they're using a > version of is_deeply() that has a known issue on older versions.
Hm, that does seem valuable. Should all test modules report their versions by default, though? Should they respect a verbose flag somewhere instead? Test::Builder could report it for them automatically, if the answer to at least one question is yes. -- c
