# from Adriano Ferreira
# on Friday 17 August 2007 11:49 am:
>The only drawback is redundant information: there are the tests and
>the list of tests. Keeping tests in "t/" with some fine way to
>discover what they are good for (according to Chris' idea) may be
>promising if not too magical.
I think keeping extra tests in "t/" is too magical for the existing
tools.
After all, I have tried it. In order to have *both* recursive tests
(which many larger projects do) *and* extra tests, you have to have
magic. My earlier attempt at this was to add test profiles to
Module::Build via file extensions which were declared in the Build.PL.
The trouble is that those don't work with EU::MM or prove or runtests
(or ack (and even vi in some configurations.))
My conclusion from that, was this "xt/foo/" thing, which requires zero
coding (or pasting) and works fine with all of the existing tools.
The "xt/foo/" thing solves that redundant information problem too.
I thought to myself, "if this works so well for what I'm doing, wouldn't
it be great if it became a sort of standard?"
--Eric
--
"Ignorance more frequently begets confidence than does knowledge."
-- Charles Darwin
---------------------------------------------------
http://scratchcomputing.com
---------------------------------------------------
