Running RubySpecs

SVN r118 implements RubySpec integration. There are a few things that you'll need to do:

1. (Optional) get a GitHub account at http://github.com
2. (Optional but highly recommended) install GIT:
• Goto the msysgit project and download the .exe based installer: http://code.google.com/p/msysgit/
• Make sure in the GIT setup that you click on the radio button labeled "Run Git from the Windows Command Prompt"
• Restart your command prompt
3. Navigate to my page: http://github.com/jflam to see the three GIT projects that you'll need to clone: ironruby-tags, mspec, and rubyspec. mspec and rubyspec are forks of the main projects so that we can add IronRuby specific tests and potential changes to mspec. The RubySpec committers can pull from these repositories to incorporate our changes. ironruby-tags is a project that contains the list of rubyspec specs that we currently exclude to get a clean regression baseline.
4. If you have GIT installed, create a directory to hold these projects. I use %USERPROFILE%\dev:
• in ~\dev\ironruby-tags run: git clone git://github.com/jflam/ironruby-tags.git
• in ~\dev\mspec run: git clone git://github.com/jflam/mspec.git
• in ~\dev\rubyspec run: git clone git://github.com/jflam/rubyspec.git
5. If you don't have GIT installed you can download the tarball using the download button in each project.

Once you have those projects in place, you'll need to grab r118 from RubyForge. There's a file in \trunk called runfirst.cmd. This will enable skip verification for projects signed with our public key, and it will create a default configuration file at %USERPROFILE%\.irconfig.rb.

If you followed my instructions and created %USERPROFILE%\dev\[ironruby-tags,mspec,rubyspec] you're good to go. If you didn't, you'll need to edit the paths in .irconfig.rb

You can test your setup by running the new regression test baseline rake task:

rake regression

r118 should report:

43 types, 1133 files, 3190 examples, 12245 expectations, 0 failures, 0 errors