rspec users - Apr 2007 - RSpec part of two (count ''em, two) GSoC projects

Here is the list of Ruby related projects accepted for GSoC. It
includes two very similar projects (seemingly the same project,
really, but I''m not saying anything ;) ) using RSpec to build a spec
suite for implementations of the Ruby language:

http://code.google.com/soc/ruby/about.html

I''m, personally, very excited about the implications of this. Thanks
to all of you who use, talk about and contribute to RSpec!

Cheers,
David (on behalf the RSpec Development Team)

On 4/12/07, David Chelimsky <dchelimsky at gmail.com>
wrote:
> Here is the list of Ruby related projects accepted for GSoC. It
> includes two very similar projects (seemingly the same project,
> really, but I''m not saying anything ;) ) using RSpec to build a
spec
> suite for implementations of the Ruby language:
>
> http://code.google.com/soc/ruby/about.html
>
Isn''t it quite symptomatic that the two RSpec GSoC projects are
essentially the same?
I guess Ruby is really in need of a test suite. As late as yesterday I
stumbled across a subtle bug in JRuby''s handling of equality in
hashes:

http://jira.codehaus.org/browse/JRUBY-807

Aslak
> I''m, personally, very excited about the implications of this.
Thanks
> to all of you who use, talk about and contribute to RSpec!
>
> Cheers,
> David (on behalf the RSpec Development Team)
> _______________________________________________
> rspec-devel mailing list
> rspec-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-devel
>

Some of you guys may know I thought about signing up for this.  I  
didn''t sign up, because Rubinus seems to already have a pretty mature  
spec library (at least for core).  Why can''t this be used for the  
other implementations?

Or is the focus on writing drivers for those implementations so that  
all of the specs can easily be run against multiple implementations?

I didn''t understand this, nor how a VM works  (and still understand  
neither), so I ended up never signing up.  I even talked to David  
Black and he didn''t have any insight on this point, so am I missing  
some big piece of the puzzle?

As far as I can tell, BDD should be used for development, hence the  
name Behaviour Driven *Development*.  So aren''t these specs just  
going to be used to develop rubinus (mainly for the stdlib)?  Once  
these are mature, then the porting should be easy, shouldn''t it?


Best,

Scott Taylor


On Apr 12, 2007, at 2:21 PM, David Chelimsky wrote:
> Here is the list of Ruby related projects accepted for GSoC. It
> includes two very similar projects (seemingly the same project,
> really, but I''m not saying anything ;) ) using RSpec to build a
spec
> suite for implementations of the Ruby language:
>
> http://code.google.com/soc/ruby/about.html
>
> I''m, personally, very excited about the implications of this.
Thanks
> to all of you who use, talk about and contribute to RSpec!
>
> Cheers,
> David (on behalf the RSpec Development Team)
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users

As for the *two*, the first listing doesn''t seem any different than  
the second.  What was going through the minds of those who wrote the  
proposals?

Scott


On Apr 12, 2007, at 2:21 PM, David Chelimsky wrote:
> Here is the list of Ruby related projects accepted for GSoC. It
> includes two very similar projects (seemingly the same project,
> really, but I''m not saying anything ;) ) using RSpec to build a
spec
> suite for implementations of the Ruby language:
>
> http://code.google.com/soc/ruby/about.html
>
> I''m, personally, very excited about the implications of this.
Thanks
> to all of you who use, talk about and contribute to RSpec!
>
> Cheers,
> David (on behalf the RSpec Development Team)
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users

On 4/12/07, Scott Taylor <mailing_lists at railsnewbie.com>
wrote:
>
> Some of you guys may know I thought about signing up for this.  I
> didn''t sign up, because Rubinus seems to already have a pretty
mature
> spec library (at least for core).  Why can''t this be used for the
> other implementations?
The intent is that the tests will be shared across implementations.

>
> Or is the focus on writing drivers for those implementations so that
> all of the specs can easily be run against multiple implementations?
>
> I didn''t understand this, nor how a VM works  (and still
understand
> neither), so I ended up never signing up.  I even talked to David
> Black and he didn''t have any insight on this point, so am I
missing
> some big piece of the puzzle?
I wish you''d joined the general discussion, but there''s still
time to
get involved in one or both projects (albeit not as a sponsored
student).
>
> As far as I can tell, BDD should be used for development, hence the
> name Behaviour Driven *Development*.  So aren''t these specs just
> going to be used to develop rubinus (mainly for the stdlib)?  Once
> these are mature, then the porting should be easy, shouldn''t it?
>
>
> Best,
>
> Scott Taylor
>
>
> On Apr 12, 2007, at 2:21 PM, David Chelimsky wrote:
>
> > Here is the list of Ruby related projects accepted for GSoC. It
> > includes two very similar projects (seemingly the same project,
> > really, but I''m not saying anything ;) ) using RSpec to build
a spec
> > suite for implementations of the Ruby language:
> >
> > http://code.google.com/soc/ruby/about.html
> >
> > I''m, personally, very excited about the implications of this.
Thanks
> > to all of you who use, talk about and contribute to RSpec!
> >
> > Cheers,
> > David (on behalf the RSpec Development Team)
> > _______________________________________________
> > rspec-users mailing list
> > rspec-users at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/rspec-users
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

-- 
thanks,
-pate
-------------------------
http://on-ruby.blogspot.com
http://on-ruby.tumblr.com
http://www.rubycentral.org/projects/soc2007

On Apr 12, 2007, at 7:11 PM, pat eyler wrote:
> On 4/12/07, Scott Taylor <mailing_lists at railsnewbie.com> wrote:
>>
>> Some of you guys may know I thought about signing up for this.  I
>> didn''t sign up, because Rubinus seems to already have a pretty
mature
>> spec library (at least for core).  Why can''t this be used for
the
>> other implementations?
>
> The intent is that the tests will be shared across implementations.
>
Yeah, I understand.  Why can''t the specs which have already been  
developed for Rubinus be used for the other implementations?

On 4/12/07, Scott Taylor <mailing_lists at railsnewbie.com>
wrote:
>
> On Apr 12, 2007, at 7:11 PM, pat eyler wrote:
>
> > On 4/12/07, Scott Taylor <mailing_lists at railsnewbie.com>
wrote:
> >>
> >> Some of you guys may know I thought about signing up for this.  I
> >> didn''t sign up, because Rubinus seems to already have a
pretty mature
> >> spec library (at least for core).  Why can''t this be used
for the
> >> other implementations?
> >
> > The intent is that the tests will be shared across implementations.
> >
>
> Yeah, I understand.  Why can''t the specs which have already been
> developed for Rubinus be used for the other implementations?
>
They can be, and it''s something Evan, Nick, Charlie, Tom, and Ola
are working on.

>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

-- 
thanks,
-pate
-------------------------
http://on-ruby.blogspot.com
http://on-ruby.tumblr.com
http://www.rubycentral.org/projects/soc2007