Front page | perl.perl5.porters |
Postings from December 2007
On Mon, Dec 03, 2007 at 05:21:10PM +0100, Gerard Goossen wrote: > Currently it t/ there are: > - base: base test, they don't use test.pl or any other module and > runnable by miniperl like they are now. > - cmd: (commands?) compound statements, etc. > - comp: compiler: op.c, toke.c and perly.y > - io: io tests, doio.c and perlio.c > - lib: testing libs (things in "lib") and testing libraries. > - op: opcodes, test the execution of opcodes, testing the code in pp*.c > - mro: method resolution. > - uni: unicode. > > should we add this list (or something like it with better description) > to t/README? Yes, I think that that's a good idea. I'm not sure what the descriptions should be. > I would like to add: > - lex: lexer tests, testing of "toke.c" and "perly.*" > current tests: t/op/chars.t, t/op/ver.t but also some of the tests in comp? > - sv: testing of SVs. sv.c, av.c, sv.c, hv.c, mg.c taint.c and gv.c > current tests: t/op/annonsubs.t t/op/array.t t/op/hash.t t/op/gv.t > - regexp: regexp tests. > current test: t/op/reg*.t They are probably a good group to break out > - arch: Architecture dependent features. > current test: t/op/64bitint.t I'm not sure if that's a great idea to break out (yet) if there's only one. > Maybe another one around scoping etc. related to 'scope.c' and 'pad.c'. Not sure. Half of pad.c's tests will relate directly to the compiler. Nicholas ClarkThread Previous | Thread Next