Re: Smoke testing Ruby

M. Edward (Ed) Borasky wrote:
> I thought that was the plan -- a merge of all the Ruby test suites,
> including the BFTS. Maybe the trick is to get whoever has the largest
> test suite to import the smaller ones??
> 
> It shouldn't matter that there's a mix of RSpec-style, Test::Unit style,
> etc. tests. And while we're on the subject, I also think it's time for a
> Big Formal Benchmark Suite. In fact, maybe the two should be the same --
> add timer calls to all the tests and assertions/"shoulds" to all the
> benchmarks.:)
> 
> Your list appears to have everything I know about, so perhaps it is
> already done.

My attempts to make this happen generally ran into the following roadblocks:

- everyone wants to use a different testing framework (test/unit, 
miniunit, rspec, minispec, runit, minirunit) and refuses to yield 
(though we're more than happy to eliminate all our minirunit stuff)
- everyone has a different idea how to structure tests...one file per 
class-under test, one file per class/method combination, one file per 
related behavior in a given class, and so on
- everyone wants to be a hero and "own" their wonderful test suite

So in the absence of any consensus, we just copied the lot into JRuby 
and have been using them that way. I'd love to see the mass suite happen 
(and it still seems like the "rubytests" project on RubyForge would be a 
great place for it), but I'm not holding my breath.

- Charlie