Re: [Perlunit-users] Using @TESTS for changing tests execution order

[Phlip <pl...@sy...>]

> >>sub test_003_delete {
> >
> >     test_002_select();
> >
> >>... delete the above  record and do some tets
> >>}
> >
> >
> > ;-)
> >
>
> Neat :) As far as I can see, the only drawback of this approach is the
> waste of time?

As one develops, one hits the test button after changing 1 to 10 lines.

If that gets slow, one spends a few minutes figuring out why and speeding it
up.

The method of last resort is to split the current folder, so its local tests
stay fast. Run the global tests before and after integrating.

If the database can't run three transactions per test run, replace it?

--
  Phlip