On Fri, 14 Nov 2003, Harry Jackson wrote:
> I have also been unable to find out if there is any sort of methodolgy
> to the testing. I have had a look through ./parrot/t/* and found a lot
> of test files but very little actual details on what each test was
> testing. I could infer from the code what each test was trying to
> achieve but some docs would be nice. If there are more docs can someone
> point me at them (I have read most of ./parrot/docs/*.pod).
Many of the tests in the t/ directory are there to test very specific,
low-level things--making sure we can create a PMC of some particular type,
or that an op works as documented. Some of the tests are a bit more
elaborate, trying to exercise full subsystems, but for the most part we're
making sure the tiny pieces work. (Which is good, as the big bits can't
work if the little ones don't)
We still don't cover all the extant op variants, and we could certainly
use larger and more abusive tests, so anything you're interested in
writing would be much appreciated.
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
