Re: Using environment variables to control long running tests (again)

2003-11-19 Thread Michael G Schwern
On Wed, Nov 19, 2003 at 07:17:46AM -0800, Randal L. Schwartz wrote: > Michael> For that reason I'd agree with Curtis and say that > Michael> everything is always run by default and users can then elect > Michael> what to turn off. PERL_SKIP_LONG_TESTS seems like a clear > Michael> name. > > As

Re: Using environment variables to control long running tests (again)

2003-11-19 Thread Randal L. Schwartz
> "Michael" == Michael G Schwern <[EMAIL PROTECTED]> writes: Michael> Disabling tests for subjective reasons (they take "too long", Michael> they don't test critical functionality, etc...) is a slippery Michael> slope. But there are clearly tests that are "tip of the iceberg" as a safety chec

Re: Using environment variables to control long running tests (again)

2003-11-19 Thread Fergal Daly
On Wed, Nov 19, 2003 at 01:45:31PM +1100, Andrew Savige wrote: > I think the two environment variables can happily coexist as > shown in the table below: > > PERL_SMOKE PERL_SKIP_LONG_TESTS > Naive User0 0 > Contrary User 1

Re: Using environment variables to control long running tests (again)

2003-11-18 Thread Danny Faught
Michael G Schwern wrote: Disabling tests for subjective reasons (they take "too long", they don't test critical functionality, etc...) is a slippery slope. I've seen this approach used successfully in a commercial setting. The key is to make sure that the long tests do get run by someone. If u

Re: Using environment variables to control long running tests (again)

2003-11-18 Thread Andrew Savige
Michael G Schwern wrote: > Disabling tests for subjective reasons (they take "too long", they don't > test critical functionality, etc...) is a slippery slope. For that reason > I'd agree with Curtis and say that everything is always run by default > and users can then elect what to turn off. PER

Re: Using environment variables to control long running tests (again)

2003-11-18 Thread Michael G Schwern
On Wed, Nov 19, 2003 at 09:30:19AM +1100, Andrew Savige wrote: > > Also, I would recommend something like PERL_SKIP_LONG_TESTS. By > > default, all tests should be run to prevent the user accidentally > > forget to run some tests. > > If some tests take hours to run, running them by default will

Re: Using environment variables to control long running tests (again)

2003-11-18 Thread Andrew Savige
Ovid wrote: > --- Kate L Pugh wrote: > > This was discussed on this list back in June. I'm wanting to > > implement it now and am wondering if Andrew's suggestion (below) has > > been taken up by anyone. Is PERL_TEST_LONG what people here > > generally > > expect to be the right environment varia

Re: Using environment variables to control long running tests (again)

2003-11-18 Thread Ovid
--- Kate L Pugh <[EMAIL PROTECTED]> wrote: > This was discussed on this list back in June. I'm wanting to > implement it now and am wondering if Andrew's suggestion (below) has > been taken up by anyone. Is PERL_TEST_LONG what people here > generally > expect to be the right environment variable

Using environment variables to control long running tests (again)

2003-11-18 Thread Kate L Pugh
This was discussed on this list back in June. I'm wanting to implement it now and am wondering if Andrew's suggestion (below) has been taken up by anyone. Is PERL_TEST_LONG what people here generally expect to be the right environment variable to set to enable long-running tests? (I know I could