Should I drag everything out of the Foo-Bar/ folder, develop and test, and copy modules and their tests back later? (Please say no.)

No, dragging is about as bad as symlinking. If you have many independent modules that you need to bring together as part of the same product, there are ways to do that (Bundle/Task, Shipwright, Dist::Zilla). For some organizational ideas see http://github.com/bestpractical/shipwright, http://github.com/bricoleurs/.

Should I write some sort of Project::Test module that controls the loading and testing of all the rest?

You could but it isn't essential, prove is pretty good.

Should I really be patching all the .t files with use lib qw{ lib/ }?

No. Let prove/Test::Harness manage @INC.

Should I patch prove?

No, subclass App::Prove :)

In reply to Re: Module-starter, using modules, and testing by Anonymous Monk
in thread Module-starter, using modules, and testing by Xiong

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.