Joseph F. Ryan wrote: > Well, my point was that language tests will be different than the > compiler/parser tests for awhile. For instance, take a simple string > substitution test: > > # simple substitution > my $var = "perl5"; > $var =~ s/\d/6/; > > While this is completely valid perl6, and something that might want to > be included in the regex test suite, it won't pass neither the P6C parser > tests, nor the P6C compiler tests, nor the P6C regex tests, because > substitution isn't implemented yet. Therefore, I don't think that it should > be included in the P6C tests. So where to put it? If it really needs to go > in /parrot/languages/perl6/t, perhaps tests like these could go in somewhere > like /parrot/languages/perl6/t/future ?
True, but keep in mind that all you're doing is submitting a patch. It's up to the pumpking to decide whether he applies it immediately or only after the feature is implemented. Go ahead and put the test where it will make the most sense once everything is finished. When you submit the patch, clearly mark that it tests a feature that isn't implemented yet. If you only have time and energy to write one test, choose an implemented feature over an unimplemented one. You'll get the most satisfaction and the Parrot project will benefit the most from tests for implemented features. Allison
