Roadmap

Integrating RubySpec and mspec

We're integrating IronRuby and the RubySpec projects to support the community-wide effort to produce an executable specification for Ruby. We will be deprecating all of our older tests that were snapshots of earlier versions of the RubySpec project over time. We will also be porting some of our older compiler / parser test suites to run under the mspec runner. This will reduce the number of technologies that we're using to run tests in IronRuby.

The RubySpec project lives in two GIT repositories, one for the specs, and another for mspec, their spec runner. If you want to contribute to IronRuby, you'll need to familiarize yourself with GIT since you'll need to at the very least be able to pull the latest versions of three test projects that we're using:

RubySpec:

This is a fork of the main RubySpec repo. We'll use this fork to test IronRuby changes / additions to the specs before integrating them back to the main RubySpec repo. There are a number of specs that simply don't work correctly under Windows, and should be changed / filtered so that they run correctly under Windows.

MSpec:

This is a fork of the main MSpec repo. IronRuby specific changes to the specs (not anticipated, but useful nonetheless) can be tested here before rolling up to the main MSpec repo.

IronRuby-tags:

This is the repository that contains the tag files (used for excluding tests) that establish what the regression baseline for IronRuby should be. A checkin to IronRuby should always pass the baseline regression tests before commit. A developer who is adding features to IronRuby is responsible for updating the tags to establish a new baseline. Note that because this project is now external to IronRuby itself, a commit to IronRuby and IronRuby-tags won't be atomic. Hopefully this won't be a problem.

See this page for more information on how to run the RubySpecs with IronRuby.