On Jan 22, 2009, at 2:24 PM, Eric Wilhelm wrote:
Or thereabouts. The business of skipping, todoing, counting,
planning,
and ensuring that all tests actually run is going to involve various
details and possibly even get into the limitations of TAP -- but you
now have every chunk of tests setup for later/encapsulated evaluation.
One way to punt toward that would be to treat each block as a single
test ala is_deeply(). A similar approach would handle loops.
You would need to modify TAP to support sub-tests. Or you can just use
Test::Class or Test::Block to divide your tests up into blocks.
This perhaps loses some granularity within each block. It also
assumes
perl 5 limitations. Possibly neither issue sticks in perl 6.
Yeah, I want that granularity. That's part of the point of the planned
count of tests.
Best,
David
