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.

In reply to Re: Naming a block function to check a group of runtime assertions by 1nickt
in thread Naming a block function to check a group of runtime assertions by Dallaylaen

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



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.