in reply to Skip Vs. Fail

I guess I am not too sure on what you mean by the "cases in between". There are only a few cases I can think of where a skipped test would be appropriate. Operating system specific code comes to mind. As does optional functionality that is dependant on packages the user doesn't have installed. Other than that I don't know why you would skip.

As for the setting the environment variables, the tests fail because at that moment, the module doesn't work because the envronment variables aren't set correctly. In my opinon those tests should fail with a message informing the user that the variables are not set correctly.

Replies are listed 'Best First'.
Re^2: Skip Vs. Fail
by Perl Mouse (Chaplain) on Dec 22, 2005 at 02:52 UTC
    There are only a few cases I can think of where a skipped test would be appropriate. Operating system specific code comes to mind. As does optional functionality that is dependant on packages the user doesn't have installed. Other than that I don't know why you would skip.
    There might be functionality only available on high enough versions of Perl - if the installed version is lower, you may want to skip tests. And some functionality (or tests) may depend on compilation settings. There's no point in testing if the module runs under threads if the installed version of Perl doesn't have threads enabled. You also might want to skip tests if the installed version has 32bit integers instead of 64 bits.
    Perl --((8:>*
[reply]

In Section Meditations