So, very quickly:1. The main goal is to have unified languages tests, that is, make language-tests would get a list of all the test files for all of the languages, and then run only _one_ harness with all those files. This would allow for one nice overview of all the tests, and tinderboxen would benefit from this too: they were reporting success as long as the last language was reporting succes.
2. In order for this to work, all the languages should have commit to having a t/harness file in their directory, responsible to get back a list of all the test files when called with a -files argument. (Except if we consider that *.t files are test files, but this may be too strict) If the language implementer wants to use this harness to also launch test for the current language only, this is of course welcome
I agree with the idea of allowing for a 'make languages-test', but I'm not sure I agree that means Parrot::Test has to be smart enough to run every language's tests directly (more below).
Well... the big problems we were make-related, with some tinder issues. Basically if any test suite died really hard the testing would stop, and only the last test suite run counted for tinder good/bad reporting.
At this point, though, I'm comfortable making it so that any language in the distribution with tests should run under the base test harness. If you need to mess around with it there's a good chance that something's gone horribly wrong, and twiddling with it on a per-language basis isn't likely the right way to go.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
