I am looking forward to experimenting with your module myself.
Great! Please let me know if you have any suggestions or criticisms. (You might also want to check the TODO and see what's already in the pipeline.)
One thing I would like to see in your tutorial, is more information about how to test with input other than integers. In my node on this subject, I showed a specification based test for a list, how would I do something like that with Test::LectroTest? Can I feed it a sampling of string data, which can be randomized/shuffled in some way? Nested lists?
That's a good idea. You can do all of those things with LectroTest, but the tutorial doesn't even hint at it. In the Generator docs, as you mention, I give some examples of list-of-list and of tree building, and in my "Free Unit Tests In Perl with LectroTest" talk for the festive Pittsburgh Perl Mongers, I showed how to build RFC 2822–compliant email addresses. You're right, I ought to cover this in the tutorial. Even if for compactness reasons I can't add a full-blown example of these uses, at least I can mention them in passing and provide pointers to relevant portions of other docs.
Thanks again for your feedback.
-
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.
|
