Best practice for unit tests that rely on internet access?
acme at astray.com
Fri Apr 29 08:33:47 BST 2011
On 29/04/11 02:15, Toby Wintermute wrote:
> c) Try to test if there's a working connection, and silently skip the
> tests if not? (Risks skipping tests if the connect fails for other
> reasons than no outbound HTTP allowed)
This module might be useful for the test:
If the module is all about testing a live service then by all means test
it. Unless it takes too long, or costs money, or might change in the
future when you don't have time to update the module...
More information about the london.pm