I'm prepared to start checking in Perl 6 tests on behalf of the Perl 6 documentation folks. These should be considered functional tests -- they are exploring the behavior we expect from Perl 6. Anything that's not yet implemented will be marked as a TODO test, and we'll figure out a way to extract the unimplemented features so people will have small tasks to accomplish.
Brent Dax had a nice suggestion for Perl 6 test organization. I like it tremendously. I repost it here to solicit comments -- to make this work, I'll need to change the Perl 6 test harness to find all of the tests. I'll also need to create several different subdirectories as appropriate. Rearranging things after the fact is a bit of a chore with CVS (if you want to keep revision history), so I welcome feedback. Brent's post follows. On Tue, 12 Nov 2002 10:01:44 +0000, Brent Dax wrote: > I don't see why we can't do this. > > t/ > var/ > scalar/ > string/ > to_bool.t > from_bool.t > ... > regress.t > num/ > bool/ > ref/ > typed/ > prop/ > taint/ > array/ > normal/ > sized/ > typed/ > hash/ > normal/ > restricted/ > typed/ > code/ > normal/ > proto/ > vari/ > curry/ > anonymous/ > placehold/ > oper/ > normal/ > arithmetic.t > string.t > list.t > logic.t > junction.t > misc.t > vector/ > arithmetic.t > string.t > list.t > junction.t > misc.t > regex/ > alone/ > grammar/ > TestGrm/ > module/ > TestMod/ > meta.t > export.t > globals.t > class/ > TestCls/ > ... > -- c
