So, I'm messing around with stuff and I got bored of writing out all
that guff in the various foo.t type tests and came up with something
that'll let me do:
foo.t
use Test::Unit::TestMaker qw/Some::Test::Class/;
run_tests;
Which is somewhat pleasant.
Of course, it'd be nice if I could do:
use Test::Unit::TestMaker
'Some::Test::Class' => {filter => qr/^test_},
'Some::Other::Test::Class' => {filter => qr/^test[A-Z]/,
todo => [qw(testNonExistentFeature)]},
;
run_tests;
But that might be running before I can walk. (The 'todo' thing could
be a tad tricky to implement. Requires holding state somewhere,
probably in the runner.)
Certainly, I've missed the Test::Harness thing of being able to mark
certain tests as 'not working yet, but run them anyway and warn me if
they go doing anything silly like passing'
Test::Harness also allows you to 'skip' certain tests depending on features
of the environment you're testing in (or possibly on whether some
other test succeeded or not, but doing test dependencies with
unordered tests seems, er, courageous)
I feel a spike solution coming on...
--
Piers
_______________________________________________
Perlunit-devel mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/perlunit-devel
