Re^4: Unit Testing in Perl

If Test::Unit does what you want, but sucks, then perhaps you could consider taking it over, upgrading it to use Test::More or some other TAP-based module, and improving it as you see fit?

As pointed out earlier I've already volunteered for this. I did get around to mailing the maintainers and never got a reply. I should really chase it up.

Comment on Re^4: Unit Testing in Perl

Replies are listed 'Best First'.
Re^5: Unit Testing in Perl by adamk (Chaplain) on Jun 28, 2005 at 08:50 UTC
Goodo! Protocol is generally that you mail a couple of times over a couple of weeks, and try any other "reasonable" way you can think of to contact them. (google for other non-stale email addresses if this is the case, etc). If the author is persona non grata, then write to the modules@ mailing list and ask to take over the module. You will be added to the authors for the module, then patch the existing version as you see fit and upload.	[reply]
Re^6: Unit Testing in Perl by adrianh (Chancellor) on Jun 29, 2005 at 16:36 UTC
Protocol is generally that you mail a couple of times over a couple of weeks, and ... Yup. I know what the protocol is - just not had the tuits available to implement it :-) Although, a maintainer recently popped up on the T::U mailing list who looks like they might be considering making some changes - so I may not need to bother.	[reply]