I would recommend against the options 2 and 3 you mentioned - for 2 because I wouldn't place any special "test mode" code into the main module, since you end up testing something different from the code that the user actually ends up running. Adding a test library has the least issues IMO, the only thing to keep in mind is that if it contains complex functions, those should be tested as well, which it's fine to do as part of the test suite. Have a look at the t folder in any of my distros, https://metacpan.org/author/HAUKEX - although I admit I figured some of it out myself, so I'm not saying everything I did there is a best practice :-)
Update: Dependencies for tests are specified via TEST_REQUIRES in Makefile.PL.
Update 2: Regarding "hide from CPAN indexer", see e.g. https://www.effectiveperlprogramming.com/2012/04/hide-namespaces-from-pause/
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|