Re: Skip tests if/unless $ENV{FOO} is set using Test::More

in reply to Skip tests if/unless $ENV{FOO} is set using Test::More

This sounds great, but the "accounting" in your example looks like a hassle. Maybe there's a good way to do the following (pseudocode):

use Test::More tests => 25;  # 25 unconditionally

...

ADDITIONAL: {
  skip "Skipping additional tests; try ENV{ALL_TESTS}\n", ADDITIONAL
    unless $ENV{ALL_TESTS};
  
  $Test::More::tests += 95;
  # 95 more tests here ...
}
[download]

--
[ e d @ h a l l e y . c c ]

Comment on Re: Skip tests if/unless $ENV{FOO} is set using Test::More Download Code

Replies are listed 'Best First'.
Re^2: Skip tests if/unless $ENV{FOO} is set using Test::More by adrianh (Chancellor) on Apr 29, 2003 at 20:00 UTC
To my eyes this looks more complex than merlyn's example. You can't do it this way since you need to know the total number of tests before the tests are run so Test::Builder can output an appropriate test header.	[reply]
Re: Re^2: Skip tests if/unless $ENV{FOO} is set using Test::More by chromatic (Archbishop) on Apr 29, 2003 at 20:56 UTC
If you're using Test::Harness of 2.0 or newer, you don't need to set a test header. It's still a good idea in cases where you can accidentally run too many tests (see the tests for File::Find, if you're lacking essential horror in your life), but it's not required. schwern's even suggested relaxing the requirement for headers in general.	[reply]
Re^4: Skip tests if/unless $ENV{FOO} is set using Test::More by adrianh (Chancellor) on Apr 29, 2003 at 21:23 UTC
Your right. Should have been clearer. You can't do it that way if you want to provide Test::Harness with a test header. Personally I like to do this since it protects me from accidentally dropping tests (many a slip between cut and paste ;-)	[reply]

In Section Meditations