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

In class today, it occurred to me that these tests could be conditional upon the presence or absence of an environment variable:

Are you saying that you were not ready for the class with all installed modules? :)

On a serious tone: Not going through all tests might reveal mistical problems and failures afterwards. Especially, if you install a module as a dependancy for another module. Sometimes things can get really deeply interconnected (thing HTML::Mason).

I am thinking more in the ways of My::Module::Simple, which would have less functionality, and therefor less dependencies and tests. It could also give a preview of what My::Module is actually doing and if I need to go through all the hassle of the full-featured installation.

Leonid Mamtchenkov

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

Replies are listed 'Best First'.
•Re: Re: Skip tests if/unless $ENV{FOO} is set using Test::More
by merlyn (Sage) on Apr 29, 2003 at 18:06 UTC
    I'm saying that the 96 CPU seconds that Math::BigInt spends running 22,000 tests (yes, literally 22 thousand tests) is not necessary for each upgrade. I'd be satisfied with about 100 key tests, and the rest could be set aside for masochists.

    I mean c'mon, testing is cool and all that, but do you really need to test 22,000 points in the whole spectrum?

    -- Randal L. Schwartz, Perl hacker
    Be sure to read my standard disclaimer if this is a reply.

      Now that you've mentioned 22,000 tests, I tend to agree more with you. :)

      Leonid Mamtchenkov

        22,000? I mere bagatelle. Take a look at Regexp::Common - over 157,000 :-)