Re: designing a test suite for multiple implementations (tools thread)

2006-08-14 Thread jerry gay
[parrot-porters and p6l have been removed from this thread, as discussion of testing tools is not directly related to those lists] On 8/11/06, Agent Zhang [EMAIL PROTECTED] wrote: On 8/12/06, jerry gay [EMAIL PROTECTED] wrote: this last testing rule i mentioned becomes somewhat problematic

Re: designing a test suite for multiple implementations (tools thread)

2006-08-14 Thread chromatic
On Monday 14 August 2006 17:20, jerry gay wrote: I've added the plan for the neutral todo mechanism to Pugs' TASKS file, getting help from many others on #perl6. The new todo marks look like this: todo :pugs6.28.0, :p6p50.110, :parrot1.00; is $got, $expected; # affected by the

Re: designing a test suite for multiple implementations (tools thread)

2006-08-14 Thread jerry gay
On 8/14/06, chromatic [EMAIL PROTECTED] wrote: Ugh, so this means editing the canonical test repository for every status-changing update to every implementation? Yuck. This seems like a problem for implementation-specific harnesses and reporting tools. this is what prompted me to start

Re: designing a test suite for multiple implementations (tools thread)

2006-08-14 Thread chromatic
On Monday 14 August 2006 18:53, jerry gay wrote: moving todo() info out of these test files leads to fragile test harnesses, as adding a test to the middle of a file will change test numbers. if test descriptions are used, then unique descriptions for each test are required. et cetera.

Re: designing a test suite for multiple implementations

2006-08-12 Thread Audrey Tang
在 2006/8/12 下午 6:15 時,Nicholas Clark 寫到: There's nothing technical stopping the Perl 6 tests being on svn.perl.org, but in a different svn repository from the current repositories, is there? Well, technically yes, except that SVK doesn't support svn:external yet. Setting a svn:external

Re: designing a test suite for multiple implementations

2006-08-12 Thread Larry Wall
[Time to stop spamming multiple lists. Followups to p6c for bikeshedding.] On Sat, Aug 12, 2006 at 10:30:22AM +0300, Gaal Yahas wrote: : On Sat, Aug 12, 2006 at 02:06:27PM +0800, Agent Zhang wrote: : is $got, $expected, todo :pugs6.2.13, :p6p50.110; : : Happily, Audrey has already

Re: designing a test suite for multiple implementations

2006-08-12 Thread Nicholas Clark
On Sat, Aug 12, 2006 at 03:32:47PM +0800, Audrey Tang wrote: ?b 2006/8/12 ?W?? 3:01 ???Ajerry gay ?g???G the question is, should it be moved into their own repository, or into the repo of the official perl6 implementation (if such a beast will indeed exist,) Currently the

Re: designing a test suite for multiple implementations

2006-08-12 Thread Gaal Yahas
On Sat, Aug 12, 2006 at 02:06:27PM +0800, Agent Zhang wrote: is $got, $expected, todo :pugs6.2.13, :p6p50.110; Happily, Audrey has already implemented the $?PUGS_VERSION variable, which can ease the implementation of such todo subs: I've added a %?CONFIGperl_compiler variable which I

Re: designing a test suite for multiple implementations

2006-08-12 Thread Audrey Tang
在 2006/8/12 上午 3:01 時,jerry gay 寫到: for managed, i have a few ideas. currently, the suite lives in the pugs repo. this is a fine first approximation, but i believe it will soon be time to move this suite (it doesn't make sense to keep the official tests in a non-official repo in the long term.)

Re: designing a test suite for multiple implementations

2006-08-12 Thread Agent Zhang
On 8/12/06, jerry gay [EMAIL PROTECTED] wrote: for managed, i have a few ideas. currently, the suite lives in the pugs repo. this is a fine first approximation, but i believe it will soon be time to move this suite[3]. the question is, should it be moved into their own repository, or into the

Re: designing a test suite for multiple implementations

2006-08-12 Thread Nicholas Clark
On Sat, Aug 12, 2006 at 09:44:38PM +0800, Audrey Tang wrote: That's assuming that the new repo, say, http://svn.perl.org/ perl6tests/, can give out commit permissions to parrot and pugs committers, yes. But as Jerry's initial motivation was moving Perl 6 tests to a more official

Re: designing a test suite for multiple implementations

2006-08-11 Thread Darren Duncan
Note: This reply is being sent to all 4 mailing lists that the original was, though I am only subscribed to the first 2 myself, for the benefit of completeness to the readers of the original. -- As my initial reply, I'll bring up 2 recent discussions or Pugs changes that

Re: designing a test suite for multiple implementations

2006-08-11 Thread Larry Wall
Just to avoid repeating some of the discussion, here's a link to #perl6: http://colabti.de/irclogger/irclogger_log/perl6?date=2006-08-07,Monsel=110#l193 The discussion goes on and off for most of the rest of the page, so you probably want to search for and highlight todo if you're using

designing a test suite for multiple implementations

2006-08-11 Thread jerry gay
recently, perl 6 development has taken the form of a multi-method dispatch. that is, multiple implementations are under active development. this includes pugs (in haskell,) v6 (in perl5,) v6-Compiler (in perl6,) and perl6 (on parrot.) hopefully, each of these returns the same result, a

Re: designing a test suite for multiple implementations

2006-08-11 Thread jerry gay
On 8/11/06, Larry Wall [EMAIL PROTECTED] wrote: Just to avoid repeating some of the discussion, here's a link to #perl6: http://colabti.de/irclogger/irclogger_log/perl6?date=2006-08-07,Monsel=110#l193 The discussion goes on and off for most of the rest of the page, so you probably want to