RE: Apache::Test order

2001-07-10 Thread Geoffrey Young
-Original Message- From: Stas Bekman [mailto:[EMAIL PROTECTED]] Sent: Monday, July 09, 2001 9:47 PM To: Geoffrey Young Cc: '[EMAIL PROTECTED]' Subject: Re: Apache::Test order [snip] Also how about specifying the order in the Makefile.PL? I think Brian Moseley has asked

RE: Apache::Test order

2001-07-10 Thread Stas Bekman
On Tue, 10 Jul 2001, Geoffrey Young wrote: Also how about specifying the order in the Makefile.PL? I think Brian Moseley has asked for the same a few weeks ago and ended up using the Makefile.PL, see the earlier thread about ordering. duh, don't know how I forgot about that - 'tis

Re: Apache::Test order

2001-07-09 Thread Stas Bekman
I've been thinking about implementing a test ordering scheme for Apache test and wanted to run it by everyone... basically from t/foo.t t/bar.t I'd like to be able to specify whether foo.t comes before or after bar.t (without calling them 1foo.t :) my reasoning is that it

Re: test order

2001-06-26 Thread Doug MacEachern
On Tue, 26 Jun 2001, Stas Bekman wrote: what do you think about this para about default sorting? I understand. Another option would be to always sort the tests unless you have specified their order on the command line. o if you specify none -- everything is sorted. o if you

Re: test order

2001-06-24 Thread Stas Bekman
On Sun, 24 Jun 2001, brian moseley wrote: i'm using Apache-Test as reference for my (greatly simplified) wombat test harness. i can't figure out how you ensure that tests are run in a specific order, or even if you are. certainly you're not in the case where you build a list of tests using

Re: test order

2001-06-24 Thread brian moseley
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

Re: test order

2001-06-24 Thread Stas Bekman
On Sun, 24 Jun 2001, brian moseley wrote: 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

Re: test order

2001-06-24 Thread brian moseley
On Sun, 24 Jun 2001, Stas Bekman wrote: ok will add 'sort'. which will presort tests before applying any other algorithm. should 'sort' be non-exclusive with 'rotate|repeat'? (it won't apply to 'random' of course) but it gets hairy then: --run-tests[=[N][:][order][:][sort]] ? I'd rather

Re: test order

2001-06-24 Thread Stas Bekman
On Sun, 24 Jun 2001, brian moseley wrote: On Sun, 24 Jun 2001, Stas Bekman wrote: ok will add 'sort'. which will presort tests before applying any other algorithm. should 'sort' be non-exclusive with 'rotate|repeat'? (it won't apply to 'random' of course) but it gets hairy then:

Re: test order

2001-06-24 Thread brian moseley
On Sun, 24 Jun 2001, Stas Bekman wrote: I understand. Another option would be to always sort the tests unless you have specified their order on the command line. o if you specify none -- everything is sorted. o if you specify only dirs -- evething within dirs is sorted, dirs order is