> Testing for the number of elements is a weak test; you really need qualitative tests as well.
> I've included most of your tests;
I think the best way to test this, is to create these strings from joining @expected arrays.
By generating these arrays one can make sure to cover all edge cases.
As a side product you'll define a formal grammar. Like:
- how are unpaired quotes to be handled?
- what about multiple whitespaces in a row?
- what about multi-line input?
- what about whitespace at start and end of string?
It would also help testing sub-regexes individually.
Crafting the strings by hand is error prone, because there are far too many cases to handle.
-
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.
|
