Beefy Boxes and Bandwidth Generously Provided by pair Networks
go ahead... be a heretic
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
For various reasons (frustration and limitations with existing modules, self-edification) I decided to write a wiki formatting module. It is a deceptively easy thing to do -- html is a can o' creepy crawlies.

Concurrently, I have an increasing level of interest in testing. So, I read everything I could lay my hands on -- the PODs for Test::Simple and Test::More, the slideshow on Petdance, and the requisite chapters in various books.

I have come to the conclusion that I somehow need to utilize WWW::Mechanize, HTML::Lint and perhaps one of the afore-mentioned testing modules to test the robustness of my hereto lame-ish but satisfying wiki formatting module.

The problem is, I have no idea how to do that. Basically, I don't want to test for things I know. I want to test for all the possible arbitrary text that users could throw, and see if my module can format it to valid html in the manner that the users expected it to do.

Would any of the knowledgeable monks (all monks are knowledgeable, some more so) kindly point me to a tutorial that does something like what I want to do? Or, could a generous monk consider putting up a tute like so?

Mérci beaucoup.

--

when small people start casting long shadows, it is time to go to bed

In reply to Wanted, more simple tutorials on testing by punkish

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others chilling in the Monastery: (3)
As of 2024-04-25 19:53 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found