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
yath -v t/foo.t
** Defaulting to the 'test' command **
( LAUNCH ) job 1 t/foo.t
( NOTE ) job 1 Seeded srand with seed '20170915' from local date.
[ PASS ] job 1 + <UNNAMED ASSERTION>
( STDERR ) job 1 App::Yath::Command::spawn is not intended to be instanciated at /Users/ollisg/.perlbrew/libs/perl-5.26.0@dev/lib/perl5/App/Yath/Command/spawn.pm line 28, <$fh> line 5.
( STDERR ) job 1 App::Yath::Command::spawn::init(App::Yath::Command::spawn=HASH(0x7fae32e4dc80)) called at /Users/ollisg/.perlbrew/libs/perl-5.26.0@dev/lib/perl5/Test2/Harness/Util/HashBase.pm line 141
( STDERR ) job 1 Test2::Harness::Util::HashBase::_new("App::Yath::Command::spawn", "args", ARRAY(0x7fae31002e50)) called at /Users/ollisg/.perlbrew/libs/perl-5.26.0@dev/lib/perl5/App/Yath.pm line 36
( STDERR ) job 1 App::Yath::run_command("App::Yath", "App::Yath::Command::spawn", "spawn", ARRAY(0x7fae31002e50)) called at /Users/ollisg/.perlbrew/libs/perl-5.26.0@dev/lib/perl5/App/Yath.pm line 24
( STDERR ) job 1 App::Yath::__ANON__() called at t/foo.t line 5
( DIAG ) job 1 Tests were run but no plan was declared and done_testing() was not seen.
( DIAG ) job 1 Looks like your test exited with 255 after test #1.
( FAILED ) job 1 t/foo.t
( REASON ) job 1 Test script returned error (Code: 255)
( REASON ) job 1 No plan was declared
================================================================================
Run ID: 1505481396
The following test jobs failed:
[1] t/foo.t
0.28497s on wallclock (0.12 usr 0.03 sys + 0.17 cusr 0.04 csys = 0.36 CPU)
Adding a ; to the end of the test works around this.
The text was updated successfully, but these errors were encountered:
Consider the test:
use Test2::V0; ok 1; done_testing
This has always worked with prove, with yath:
Adding a ; to the end of the test works around this.
The text was updated successfully, but these errors were encountered: