Without regard to the code itself, I'd break the test into parts. First I'd test that I get a response from the object instantiation. Then, I'd test to see if it showed the network device attached. Based on the result of the previous test, I'd test communicating with the device or skip this test.

It sounds, though, like your code doesn't have this kind of granularity for the test suite to test. Perhaps you should consider creating the object either way, as you already suggested. You could then have a status method for it which reports presence or absence of the device. Further future tests could be skipped if the device is not determined to be present.

In reply to Re: The chicken and the egg (or how do I pass the module test) by mr_mischief
in thread The chicken and the egg (or how do I pass the module test) by ruzam

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.