Yukihiro Matsumoto:
> test/* is no way to test Ruby, it's test suites for MRI. You know the
> difference.
Matz,
We all know the difference. The question is, as Ruby the language evolves, why would CRuby developers not use RubySpec to specify *language* behavior (which is what a lot of test/* tests currently do)? Right now there is a fair share of
duplication of effort going on and it is disappointing. What testing framework produces what output is a red herring: that can be easily changed in a week.
I think not using RubySpec as the primary test suite for every Ruby implementation (including MRI) is damaging to the long term Ruby competitiveness/relevance. Fragmentation is a terrible thing for developers. This does not go hand in hand with the (stated) goal of Ruby to make developers happy.