Not knowing the details of your tests, I'm not sure if this is directly applicable. However, I can tell you about something similar I've done. In my Class::Tiny::ConstrainedAccessor, I need to run the same tests against about five different upstream modules. I put the tests in a common module. I then have a separate *.t file for each upstream module (each test condition). Each *.t file loads the common module and the upstream module, then passes the upstream to the test runner in the common module ( example). The common module does not have a test plan or a done_testing() call, so it fits seamlessly into the framework provided by the *.t file.
-
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.
|
