Your solution will probably work too, but I've found a simpler solution - less changes in current code.

I just iterate over all tests on my own using TAP::Parser and now top-level TAP::Harness is happy.

#!/usr/bin/perl
use strict;
use warnings;
use TAP::Harness;
use TAP::Parser;
use Test::More 'no_plan';

my $tap = TAP::Harness->new(
    {   'color'     => 1,
        'verbosity' => 1,
        'lib'       => ['lib', 'blib/lib', 'blib/arch'],
        'timer'     => 1
    }
);

my @tests = (glob('t/unit/**/*.t'), glob('t/unit/*.t'));

foreach my $test (@tests) {
    my $parser = TAP::Parser->new({source => \$test});
    while (my $result = $parser->next) {
        next unless $result->is_test;
        ok($result->is_ok, "[$test] " . $result->as_string);
    }
}

ok(1, "Unit tests run");
[download]

---

---

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! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

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:
	&		&
	<		&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.