On Sun, 24 Jun 2001, Stas Bekman wrote:
> the only way to ensure identical order from run to run,
> across different systems (and changes in file inodes
> ordering) is to explicitly list the tests in the wanted
> order. otherwise it's up to the inodes order under ./t.
>
> Since I mess with tests anyway now (see my other post
> from a few minutes ago), do you want to add yet another
> mode 'sort'?
makes sense. that would allow me to at least use naming
conventions to ensure run order.
> But, hey, look at the random mode I've just added. Why
> would you want to ensure the same order in tests? That's
> not the way QA works :)
dependencies. if class B extends or uses class A, i want to
run the tests for class A before those for class B.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
