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

2006-08-15 Thread Nicholas Clark
On Mon, Aug 14, 2006 at 07:12:06PM -0700, chromatic wrote: > PS - sbk30, please don't send me any more automated followup messages. Fix > your mailing software. I've found that our resident neighbourhood BOFHs have been very helpful at forcibly un-subscribing anyone anti-social enough to be se

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. Su

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 th

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 :pugs<6.28.0>, :p6p5<0.110>, :parrot<1.00>; > >is $got, $expected; #

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