Re: Perl 6 Test Organization

> If people are happy to use these data-oriented test-scripts, then I'm
> happy to examine various groups of tests and find their abstractions.
> It's just basic data-modeling, applied to source code. By modeling
> each file independently, I avoid the problems associated with
> infinitely flexible abstractions. I usually find that after a few rounds
> of refactoring, some of the abstractions become reusable.

So, we can either use one generic test script, and write the perl6
ourselves...or
we can create N specific test scripts which generate the perl6 for us given
a particular data set and after we have written the perl6 ourselves.  Sounds
like duplication of effort and a maintenance problem to me.  I would rather
stick with writing the perl6 and its output.

Tanton