You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When an exception object is thrown from a test control method while using prove, the contents of the object are dumped to the screen rather than the stringified object.
For instance, with:
packageTestsFor::Exception;
use Test::Class::Moose;
use Throwable::Error;
subtest_setup {
Throwable::Error->throw('goodbye');
}
subtest_ok {
ok(1);
}
packagemain;
use Test::Class::Moose::CLI;
Test::Class::Moose::CLI->new_with_options->run;
Note that this does not happen with yath. It could arguably be a bug in the Test2 TAP formatter. However, it is limited to exceptions in TCM test control methods.
The text was updated successfully, but these errors were encountered:
Something somewhere has decided to Data::Dumper::Dumper the argument it was given instead of just stringifying it. I'm not sure what in the chain is doing that, but it's well after the flow of execution leaves TCM.
When an exception object is thrown from a test control method while using
prove
, the contents of the object are dumped to the screen rather than the stringified object.For instance, with:
You get these 614 lines of output.
Note that this does not happen with
yath
. It could arguably be a bug in the Test2 TAP formatter. However, it is limited to exceptions in TCM test control methods.The text was updated successfully, but these errors were encountered: