comment on

No.

I believe that the test suite should be an entirely optional part of the distribution. If I choose to skip the "make test" step, I do not need the module at all.

However, test suites are important, and having that extra module can certainly help you find bugs earlier and thus eventually help me, the user of your module.

For Test:: modules, I prefer that they are included in the distribution (like Test::More often is). It does mean that you, the module author, have more to maintain.

Even if your module itself can use certain modules, that does not always have to mean you have to depend on them. For example, DBIx::Simple can use SQL::Abstract, DBIx::XHTML_Table and Text::Table, but if the user decides not to use that functionality, they're never even loaded. This means more work for the users who do wish to use these features, but at least *they* can choose.

Juerd # { site => 'juerd.nl', plp_site => 'plp.juerd.nl', do_not_use => 'spamtrap' }

In reply to Re: Should a CPAN module list Test:: modules as dependencies? by Juerd
in thread Should a CPAN module list Test:: modules as dependencies? by grinder

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.


We don't bite newbies here... much
	PerlMonks