I think it is certainly reasonable to automatically test for system dependences before running the test suite. In your case, you need to ensure that the network is up and that certain services are available and listening, etc. As a part of this setup, you will learn IP and ethernet addresses that could be used in the test suite.
Once the initial setup is done, however, it would be best to arrange your test suite so that tests do not rely on any other system dependent stuff other than what was gathered during setup. The point of testing is to validate known output against known input, so reporoducibility is key and the actual test suite should be as machine independent as possible. This sort of attitude also helps you to eliminate implicit machine dependencies in the code you are testing.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
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:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.