The YAML Specification is independent of the YAML perl package.
I use YAML for all my human-readable configuration files and have even used YAML for this specific purpose. Here's a sample test from the test suite (actions map directly to Test::WWW::Mechanize methods):
- url: BLAH.cgi
title_is: My Spiffy Page
actions:
- submit_form_ok:
form_name: magic_form
fields:
mstat: M
mtype: 99
- contains:
- Mbr First
- Mbr Last
- lacks:
- Amt Due
- submit_form_ok:
form_name: magic_form
fields:
# delcd will still be 'A'
mstat: ""
amdue: 50
chk_amdue: checked
- contains:
- Mbr First
- Mbr Last
- Amt Due
Update: My employer (National Financial Management) has granted me permission to modify and release the test driver for these files on CPAN. Watch for Test::WWW::Mechanize::YAML on CPAN!
Update 2: Released Test::WWW::Mechanize::Driver on CPAN!
-
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.
|