On 15 Aug 2006, at 19:29, Michael Peters wrote:
[snip]
I think this is the most important benefit. Test runs aren't bound
to the single
time it was run with a certain harness. They can be captured and
viewed later by
the same developer or shared among developers.
Nothing stopping you doing this with JUnit/TestNG/whatever either.
You don't have a protocol, but you do have a standard set of class
based APIs. Not that hard to stick a proxy/recorder type thang in the
middle.
What TAP might give you is the idea of a "standard" though -
something to make it easier for different folk with different tools
to more easily have a common language..
I'm actually hopeful that Smolder (http://sourceforge.net/projects/
smolder) or
something like it will show how useful abstracting out the test
output from the
harness can be. I'm planning on doing a 1.0 release of it pretty
soon if
anyone's interested.
Me! Me! I've already had a brief play and am considering using it at
$WORK.
Adrian
