I personally would make it an author test that requires the AUTHOR_TESTING env var.
I have apent too much time debugging network tests that fail because a file moved, a domain was down/expired, or the connection was not sufficient, but present. There are also corperate/school blacklists/whitelists. Any number of things outside your control. Run the test for release, but do not aubject evertone to these uncontrollable failure cases. On Nov 12, 2017 7:00 AM, "James E Keenan" <jkee...@pobox.com> wrote: > Is there any code which is considered "best practice" for "skip_all unless > I have an Internet connection"? > > For the first time I want to write a library whose tests will benefit from > connection to an FTP server. If there is some code that I could just drop > in for situations where the test suite is run offline, that would be > helpful. > > Thank you very much. > Jim Keenan >
