On 20 Jan 2007, at 23:50, Andy Lester wrote:
Obviously, nothing will get renamed to Test::Harness without Andy
Lester's blessing. Further, nohing will simply be 'rushed into
place'
without extensive testing and we want to feel *extremely* comfortable
that we're not going to break anything. We want this to be
*completely* backwards compatible, but would like to hear feedback
from
folks about any issues we might want to be aware of.
What I would see is that what you have would become Test::Harness,
and I would hand maintainership of Test::Harness to you. What you
have as runtests would be renamed to prove, and it would be prove-
compatible up to this point.
As Curtis mentioned I'm working on the T::H compatibility layer at
the moment.
Initially I'm concentrating on Test::Harness itself - implementing
runtests and execute_tests as thin wrappers around TAPx::Harness et
al. That's going well but I keep glancing nervously at the pluggable
Straps mechanism. Straps.pm has the warning:
"THIS IS ALPHA SOFTWARE in that the interface is subject to change in
incompatible ways. It is otherwise stable."
It would be great if 'incompatible ways' could be interpreted as
'replaced entirely by TAPx::Parser' but I don't know how well that
would fly :)
What do people think?
--
Andy Armstrong, hexten.net
