Hi,
to allow for moving them to a test script after good enough testing environment is available.
What does this mean? I don't see anything in the code you showed that cannot be in a normal test file run under the test harness. Can you expand on this?
use Test::Most;
use_ok('My::Module'); # via FindBin, `use lib`, if needed
subtest 'bloated_untestable_method' => sub {
ok( my $foo = My::Module->bloated_untestable_method, 'instantiate'
+ );
like( $foo->{bar}, qr/f?o?r?m?a?t/, 'value of `bar`' );
subtest 'baz' => sub {
can_ok( $foo->{baz}, $_, "`baz` can `$_`" ) for qw(do_this do_
+that frobnicate);
};
};
The way forward always starts with a minimal test.
-
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.
|