in reply to Testing perl modules that rely on remote data

My approach to testing "online sites" is to copy the HTML and to test against that locally. That way, your tests don't deliver bogus messages just because the network is unreachable or the site is down for maintenance. You could distribute the online tests separately, or only run them when an environment variable is set, to verify that the site does not change behind your back.

  • Comment on Re: Testing perl modules that rely on remote data