# The RubySpec project at rubyspec.org

**URL:** <https://www.ruby-forum.com/t/the-rubyspec-project-at-rubyspec-org/137626>\
**Category:** Ruby\
**Created:** [May 14, 2008, 8:57pm UTC](https://www.ruby-forum.com/t/the-rubyspec-project-at-rubyspec-org/137626 "2008-05-14T20:57:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![brixen](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/278dde/32.png) [@brixen](https://www.ruby-forum.com/u/brixen)\
**Post date:** [May 14, 2008, 8:57pm UTC](https://www.ruby-forum.com/t/the-rubyspec-project-at-rubyspec-org/137626/1 "2008-05-14T20:57:44Z")

</div>

Hi all,

The RubySpec project is now officially hosted at [http://rubyspec.org](http://rubyspec.org).  
The project aims to write a complete executable specification for the  
Ruby programming language based on RSpec-style specs. The project  
started as a glimmer in the eye of an early Rubinius (http://  
[rubini.us](http://rubini.us)) contributor and has since grown to over 6900 examples and  
25600 expectations, with contributions from many dedicated folks.

The RubySpec sources have been part of the Rubinius repository for  
nearly 1.5 years and there are some growing pains from splitting off  
into a separate project. The rough edges are being worked out, but we  
appreciate your patience.

You can review the (growing) documentation here:

[http://rubyspec.org/wiki/rubyspec](http://rubyspec.org/wiki/rubyspec)

Related to the RubySpec project is a customized RSpec-syntax  
compatible framework for running the specs named MSpec. We intend to  
keep the specs compatible with RSpec, but beginning Ruby  
implementations often cannot run RSpec until a lot of Ruby language  
features are implemented. You can review the MSpec documentation here:

[http://rubyspec.org/wiki/mspec](http://rubyspec.org/wiki/mspec)

You can review how the Rubinius project is incorporating the RubySpecs  
here:

[http://rubyurl.com/9xFd](http://rubyurl.com/9xFd)

We would love to have your help on this project. With all the great  
work being done on the many Ruby implementations, we want Ruby’s  
version of “write once, run anywhere” to be solid gold. One of the  
best ways to ensure this is to have an unambiguous standard. Charles  
Nutter has already put out a call for participation:

[Headius: RubySpec: Bringing Ruby Test Suites Together](http://headius.blogspot.com/2008/05/rubyspec-bringing-ruby-test-suites.html)

Please join us.

Finally, thanks to Engine Y. for donating hosting for the  
[http://rubyspec.org](http://rubyspec.org)  
website and for their significant support of the RubySpec project both  
as part of Rubinius and as part of the Ruby community as a whole.

Cheers,  
Brian

---

<div class="post-metadata">

**Author:** ![brixen](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/b/278dde/32.png) [@brixen](https://www.ruby-forum.com/u/brixen)\
**Post date:** [May 15, 2008, 4:48pm UTC](https://www.ruby-forum.com/t/the-rubyspec-project-at-rubyspec-org/137626/2 "2008-05-15T16:48:39Z")

</div>

On Wed, May 14, 2008 at 8:56 PM, Brian F. [removed\_email\_address@domain.invalid](mailto:removed_email_address@domain.invalid) wrote:

> nearly 1.5 years and there are some growing pains from splitting off  
> into a separate project. The rough edges are being worked out, but we  
> appreciate your patience.

this is very good news! the project will now probably receive the  
attention  
it deserves.  
thanks to all contributors.  
– henon
