comment on

Personally, I think using Module::Starter to create your test module is overkill, as most of Module::Starter is oriented to creating a framework for packaging up modules for distribution which you don't really need.

I've been using ExtUtils::ModuleMaker instead of Module::Starter, though both focus on getting a developer started.

i'd disagree about them being overkill, though, because they do create the basic organizational structure (directories, stub test files, etc) to get one in the habit of testing.

additionally, at least ExtUtils::ModuleMaker has options to create multiple modules, which is *very* convenient.

In reply to Re^2: Application Testing: Custom Module or Perl Test Files? by geektron
in thread Application Testing: Custom Module or Perl Test Files? by ghenry

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.


laziness, impatience, and hubris
	PerlMonks