Subject: | Two requests for enhancement |
Date: | Mon, 23 Feb 2009 11:36:06 -0600 |
To: | bug-Test-Command [...] rt.cpan.org |
From: | Lanny Ripple <lanny [...] cisco.com> |
Hi Daniel,
Thanks for writing Test::Command. I've written a module that uses
it and it saved me a lot of time. (I never would have gotten exec
and saving stdout, stderr as cleanly.)
I have two requests for enhancement. The first is that you add a
:internals
export to expose your internals. Test::Command does not subclass
well (you explicitly test $cmd refs as =~ 'Test::Command') and the
internals are useful in their own right. I use full naming to get
to them which works well enough but my code would look a bit cleaner
without the full names. (Ok. This is a pretty low priority request.)
The other request is that you make available the low order bit
information currently thrown away from the system call. I have a
long series of tests via Test::Class that uses Test::Command. If I
want to quit the test run and type ^C the I-want-to-stop information
is thrown away by Test::Command.
Thanks again for such a useful module,
-ljr