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 variable to set to enable > > long-running tests?
I followed merlyn's suggestion and used PERL_SMOKE. That is, the long- running tests are skipped by default; they are run only if the user sets the PERL_SMOKE environment variable. Since the name is arbitrary, it makes little sense for each developer to invent her own different name for the same purpose, hence my initial query. > I don't know if something like that's been implemented or not, but I > think it's something that should be implemented by the user and > probably not be pushed into the core testing suite. Having an agreed name requires no changes to any test harnesses, the user controls simply by setting the PERL_SMOKE environment variable. > 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 annoy interactive users, in particular those running the CPAN shell. /-\ http://personals.yahoo.com.au - Yahoo! Personals New people, new possibilities. FREE for a limited time.
