I think that when 5.8.0 is released, Test::Simple/Builder/More should
be at or near 1.0. Seems as good a time as any. This means the API
will have solidified: any experimental features will be resolved one
way or the other, and no more backwards incompatible changes past that
point (not that there have been any really).
So, call for features. Anything missing? Anything people want/need?
Any requests you've sent that I've ignored? Any requests you've sent
that I've said are batty, try 'em again.
My current TODO list is surprisingly small. Here's what I've got:
Test use_ok() with imports better.
Add BAIL_OUT() (little known Test::Harness feature that basically
declares that the universe has turned out all wrong and the test
will now stop what it's doing and just go back to bed.)
Add a way to ask "Are we passing so far?". Probably a
Test::Builder method.
eval_ok(). A replacement for this sort of thing. My main concern
is that it not screw up caller().
my $result = eval { some_stuff };
is($@, '', 'didn't explode');
is($result, 'something', 'and it ran');
Add something like Test::More->builder to replace direct calls to
Test::Builder->new.
Decide if there's any reason why Test::Builder shouldn't
be a singleton.
Expose Test::Builder->diag in Test::More.
Write a numeric equivalent to is().
Write a version of like() that can emulate:
ok( $foo !~ /bar/ );
Finish (start?) Test::FAQ
Expand the Test::Tutorial
Decide if the exit code behavior on failure is a useful default
case.
I've only ONCE before had a module actually reach 1.0, and it has one
function. So this is a Big Thing for me.
--
Michael G. Schwern <[EMAIL PROTECTED]> http://www.pobox.com/~schwern/
Perl Quality Assurance <[EMAIL PROTECTED]> Kwalitee Is Job One
gleam comes to my eyes
as I combine pure water
and triticale.
-- mjd
