On 03/07/06, Adam Kennedy <[EMAIL PROTECTED]> wrote:
> 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.
"2. I don't want to have to count up the total number of tests in my
file but I do want the protection of the plan"
The "protection of the plan" is that when my script exits cleanly but
prematurely I find out. That's the only protection it gives.
Currently, the only way to get this protection is to count up all of
the tests. This grouping scheme does not change that.
The other objectives aren't terribly important to me (and I'm not even
sure #3 is solving the right problem).
The addition of groups will not change that behaviour in unplanned test
space, because what you want is a simply unknowable.
I'm not arguing about unplanned test space,
F
