Did you write the test script before or after writing the module? Writing tests early accrues many benefits.
I think it's appropriate that you're using the same (perl) file permission techniques in the module and the script; that makes the test script more portable and easier to maintain than if you checked file permissions using Linux or Windows specific techniques, for example. After all, you're not testing perl itself, you're testing your module: you want to demonstrate, via your test script, that your module has a nice, clean, portable, easy to understand interface, and is easy to test in isolation. Testing file permissions in a non-perl way, while a good idea for testing perl itself, introduces unnecessary complexity and an unwelcome dependency for your module's test suite.
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:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- 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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||