As others indicate, there is little in the testing modules that relys on tests being in ".t" files. It's a feature for you to use, or not use. It's a very handy convention that will be understood widely, but as always, TIMTOWTDI.
A really wonderful book on testing, IMO, is Perl Testing: A Developer's Notebook. It's a compact and concise presentation of "here's how to do it" code examples, with supporting explanatory text to take you through the examples quickly. It covers a very wide range of testing scenarios, but it's organized so you don't have to read much more than just the section you're interrested in.
You can take a look at a sample chapter of the book on-line at the O'Reilly website. The book's Amazon rating is high, but there are a few who really didn't like it, so it's probably a good idea to take a look at the sample.
-
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.
|