It seems to me that you are going about it all wrong. If you want to check the web server configuration, why not just check the web server configuration? Modules already exist to parse the Apache configuration format, etc. Instead of testing the indirect result (which may be influenced by other things), go to the source. You already need access to the web server to put your HTML files there. See if you can find the configuration files too.

If you want to check HTML that comes back from the webserver, there are already plenty of HTML testing modules out there. You don't need to come up with your own module because you have a particular use for these things. Test::Harness, Test::WWW::Mechanize, etc. can already do the sorts of things you need and already provide a widely-used, widely-tested, and generally accepted way of doing things. Modules such as HTML::Tidy, Test::HTML::Tidy, and the like will help you do more while writing less of your own code.

It seems to me that a better name would be something such as Test::WWW::Server::VerifyFeature. In any case, you need to find a top level namespace for this.

Good luck :)

--
brian d foy <brian@stonehenge.com>
Subscribe to The Perl Review

In reply to Re: CheckWeb - a new module by brian_d_foy
in thread CheckWeb - a new module by pileofrogs

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.