On Thu Sep 20 13:03:31 2007, [EMAIL PROTECTED] wrote: > http://perlsix.org/svn/parrot/view/branches/unified_testing/BRANCH_TODO > > > Goals: > > Completely unified testing. [snip] > 5) Add processing of the output of Configure --test. >
When I began working on writing tests for the Perl 5 components of Parrot last November, we made the decision to not incorporate all the tests I was writing under the 'make test' target. In part that was because some take a long time to run and in part because some of the tests were only meaningful if run post-configuration, pre-build -- so running them during 'make test' (which is post-build) didn't add up. The tests of the build tools were placed under 'make buildtools_tests'. Later tests I wrote for Parrot::Manifest were similarly placed under 'make manifest_tests'. The build tools tests are a subset of the tests which are run when you call 'perl Configure.pl --test'. They (along with tests in t/postconfigure/) are also run when you call 'perl Configure.pl --test=build. All of the above test suites ought to be run by Parrot developers working in the areas they cover (config/, lib/Parrot/Configure/*, lib/Parrot/Pmc2c/, lib/Parrot/Ops2c/, lib/Parrot/Ops2pm/, lib/Parrot/Manifest/, etc.) but -- as much as I'm in love with my own creations -- it's not clear that they need to be run every time anyone says 'make test'. So I'm unclear as to what the 'unification' you're talking about would mean for these test suites. Can you clarify? Thank you very much. kid51
