Friends,
In the kid51/testsets2 branch I have developed functionality to run
'make fulltest' as one overall harness (with one summary for all tests)
rather than as a succession of harnesses. In addition, I have developed
a 'make smolder_fulltest' target which will create an archive of a 'make
fulltest' run and upload the archive to our Smolder server.
This picks up a line of work begun by Jonathan Leto earlier this year.
At first I began working in the branch which Jonathan developed, but
then I realized it was a considerably more complex problem, so I started
a fresh branch.
In the course of developing this functionality, it seemed wise to
disentangle some of the code underlying the current master version of
t/harness. So now we designate groups of tests via a new package,
Parrot::Harness::TestSets. Some code in Parrot::Harness::DefaultTests
and t/harness was revised accordingly.
t/harness has accrued a lot of cruft over the years, so it seemed best
to create a separate program, t/fullharness, to underlie 'make fulltest'
and 'make smolder_fulltest'. Getting a single-overall-harness for 'make
fulltest' was not too difficult. But getting 'make smolder_fulltest'
forced me deep into the guts of TAP::Parser and TAP::Harness::Archive.
The result was two subclassing packages,
TAP::Harness::ReportByDescription and
TAP::Harness::Archive::MultipleHarnesses. I've included them in Parrot
under 'lib/', but I'll be discussing with the authors of their parent
modules how to get them on CPAN. The documentation for these packages
is not yet in good shape.
Here is an example of the output from 'make smolder_fulltest':
http://smolder.parrot.org/app/projects/report_details/24016
'make smolder_fulltest', like 'make fulltest', will probably be useful
be useful (a) in preparation for releases or (b) in preparation for
merges of large branches.
Please review. Thank you very much.
Jim Keenan
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
