That seems like a problem too but the one I'm trying to get at is
4 no plan, with groups
If your script exits prematurely after one of the groups, the harness
will not notice because everything looks just fine. The solution to
this is not to use "plan, with groups" because then you have to count
all the tests individually which goes aginst objective #2,
But then we've had this problem up till now anyway.
If it exists prematurely with a "good" return code now, it's a correct
ending, if it returns with a bad return code it's an error.
The addition of groups will not change that behaviour in unplanned test
space, because what you want is a simply unknowable.
Adam K
