# from demerphq
# on Monday 10 September 2007 10:51 am:
>> As to the core tests, they trip up like crazy, I think because they
>> are not original in their choice of names for temporary files.
I solved that in dotReader's tests with some '. $$' action.
I was playing with the 't/' directory from perl-5.8.8 last night and
having very little luck. For starters, I had to hack t/TEST to print
the filenames, but still came up with 995 files instead of 933, so I
think I did it wrong ;-)
>When you say core tests which do you mean? The ones that test modules
>or the ones that test core? ...
>Its the module tests which really take a while.
Probably the core module tests. And/or both.
I currently have no partitioning for what runs in parallel or "groups of
series" (ala `make -j`.) I supposed grouping by directories could be
an easy switch-activated feature. In general though, I'm thinking this
ventures into the realm of "test metadata", so I hesitate to ad-hoc too
much into it.
--Eric
--
Anyone who has the power to make you believe absurdities has the power
to make you commit injustices.
--Voltaire
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
