On Sun, Jan 13, 2008 at 10:54:57AM +0100, Cosimo Streppone wrote:
> I had discussed the [S29/subdir/*.t] structure with
> particle over irc, but probably I misunderstood.
>
> So I'd better change these tests to something like:
>
> t/spec/S29-str/chomp.t
> t/spec/S29-str/p5chomp.t
> ...
> t/spec/{syn_number}-{syn_section_title}/{function}.t
>
> Is that ok?
Yes, I like this much better. Perhaps more generic is:
t/spec/{syn}-{section}/{name}.t
where "syn" is the corresponding synposis or chapter,
"section" is the major section heading for the features
being tested, and "name" is anything that conveniently
identifies the tests.
I choose "name" instead of "function" for the last part,
because I don't want to imply a 1-1 correspondence between
test filename and function names. Sometimes we're testing
something other than a function, some tests are better
organized by a feature other than their name.
Similarly, the "section" doesn't have to correspond
strictly to existing headings in the Synopses. Larry
has already commented [1] that we should think of
the current sections in each synopsis as being
guidance and not cast in stone. So, when choosing
how to name a section, I typically also look to the
p5 camel to decide how to choose a section name.
Lastly, we should probably move this thread to
<[EMAIL PROTECTED]>, which is focused on
Perl 6 implementations and the test suite.
This list is really more for discussions about
Parrot.
Thanks!
[1] http://www.nntp.perl.org/group/perl.perl6.compiler/2007/12/msg1668.html
