Your test assumes a common, though not guaranteed, environment and would fail in several modes. Things that come to mind are:
- restricted localhost traffic
- non-root user trying to bind port 80
- IPv6-only systems (?)
I'd say none of these really are your code's fault. Asking the testing user for environment details that should work for them seems pretty fair to me, even if you have (understandable) reservations. This reminds me of the Astro::SpaceTrack module I use for work (e.g. its query test). I'm sure there are other ways of doing this, though.
Alternatively, stick with localhost as a default and simply skip over the tests if the basic HTTP traffic fails. If you want to filter out noise in failure reports, have things fail with a reference error/warning text that's easy for you to filter out as noise.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||