Beefy Boxes and Bandwidth Generously Provided by pair Networks
Pathologically Eclectic Rubbish Lister
 
PerlMonks  

Re: Private tests - How to setup?

by CardinalNumber (Prior)
on May 28, 2008 at 21:51 UTC ( #688935=note: print w/replies, xml ) Need Help??


in reply to Private tests - How to setup?

Backing up your assumption and kyle's comment, for the behavior you're describing (skipping pod coverage tests, etc.), the current recommended practice is to check an environment variable, specifically $ENV{RELEASE_TESTING} and skip_all() based on whether it's true/false. I say 'current recommended practice' because there is no real standard, AFAIK.

I used to use $ENV{AUTHOR_TESTING} in my distributions but $ENV{RELEASE_TESTING} is the hot new thing decided upon during the Oslo QA Hackathon.

Update: For quick .t examples, see the Oslo QA Hackathon 2008/Achievements wiki page.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://688935]
help
Chatterbox?
and all is quiet...

How do I use this? | Other CB clients
Other Users?
Others chanting in the Monastery: (11)
As of 2016-12-06 21:11 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    On a regular basis, I'm most likely to spy upon:













    Results (117 votes). Check out past polls.