From: Urabe Shyouhei <shyouhei@...>
Date: 2011-09-09T10:54:44+09:00
Subject: [ruby-core:39401] Re: RubySpec vs CRuby's test/...

(09/09/2011 07:28 AM), Charles Oliver Nutter wrote:
>> Shouldn't ruby-core help maintain an implementation-agnostic Ruby
>> behavioral test suite? If so, why isn't that happening, and why
>> couldn't it be RubySpec? If not, why not?
> 
> I'm going to try to dial back the rhetoric a bit and lay out the
> facts. Jump in where I go astray.
> 
> THE NEED:
> 
> * There must be a test suite all Ruby implementations can use to
> confirm that they are compatible with "Ruby" the
> language/core/libraries
> 
> * This suite must not be specific to any one implementation, and
> should only include tests for features considered "standard" Ruby
> (i.e. not implementation-specific).

And I think RubySpec is insufficient for this purpose.  It describes
what CRuby is now and never specifies what it should be.  I don't
want to say that's a standard to obey.  For Ruby alternatives, RubySpec
shows you a way to go.  Sadly it won't for CRuby.