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); }; };
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
For: | Use: | ||
& | & | ||
< | < | ||
> | > | ||
[ | [ | ||
] | ] |