Kent, I'm not sold on this. The existing author/release/automated test environment variables define categories of tests that testers opt into. What you're describing is a variable to detect a capability. It's closer to NONINTERACTIVE_TESTING, but note which way the defaults go -- the assumption is that interactivity *is* available unless told otherwise. And the reason for the variable in the first place is that prompting can hang. Avoiding hangs is a higher priority for me than avoiding failure. I'd be more interested in seeing a standard way to probe the capability rather than rely on testers to declare capabilities. use Test::RequiresInternet; # or skip_all Or, if particular hosts/ports need to be reachable: use Test::RequiresInternet { "www.google.com" => 80 }; David -- David Golden <xdg@xdg.me> Twitter/IRC: @xdgThread Previous | Thread Next