I'm wondering why I should think about switching from Test::Simple to Test::More.
If you're doing anything non-trivial it will probably help.
What is it that gives Test::More its "Moreness" ?
It gives you more expressive ways to talk about your tests. So instead of saying:
ok ( $foo =~ /bar/, 'contains bar');
ok ( UNIVERSAL::isa($o, 'MyClass'), 'isa MyClass' );
ok( $foo eq 'bar', 'equals bar' );
you can say
like( $foo, qr/foo/, 'contains bar' );
isa_ok( $o, 'MyClass' );
is( $foo, 'bar', 'equals bar' );
which is marginally easier to comprehend. You also get more informative test failures, for example if you do:
is( 'apples', 'oranges', 'expecting to find some oranges' );
you'll get the informative
not ok 1 - expecting to find some oranges
# Failed test (-e at line 1)
# got: 'apples'
# expected: 'oranges'
rather than just
not ok 1 - expecting to find some oranges
You'll find the same sort of advantages with other Test:: modules. You get to express you test more precisely and you get better feedback on test failures.
-
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.