This is an abbreviated version of what you will find at Howto - Develop with a separate RubySpec repo. Refer to The Rubinius specs for more documentation on the specs.
Then, follow these steps to write a spec for a Ruby method:
-
Edit a file under
spec/ruby/1.8/... -
Run
bin/mspec -tr spec/ruby/1.8/some/spec_file.rb - Repeat until the spec passes on MatzRuby
-
Run
rake git:statusORcd spec/ruby; git status -
Change directory to
spec/ruby -
Run
git status, git add, git commit, etc. -
Run
git format-patch - Upload the patch in a ticket on the rubyspec.org website
You're done. When your patch is accepted, you will get a commit bit to the RubySpecs repository. However, while you're on a roll, why not add a patch for Rubinius as well. See Howto - Fix a failing spec.
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
0.10—69% complete
Completed 9 of 13 tickets
Pages
- Home
- FAQ
- IRC Info and Who's Who
- Releases
- Using Git
- Installation
- Getting Started
- Common Build Problems and Solutions
- Howto - Contribute
- Howto - Write a ticket
- Howto - Run my Rails app with Rubinius
- Howto - Write a Ruby spec
- Howto - Write a Rubinius spec
- Howto - Fix a failing spec
- Howto - Develop with a separate RubySpec repo
- Howto - Debug shotgun
- The Rubinius specs
- Shotgun - The Rubinius Virtual Machine
- Developer Readme
- Core Library - Coding Guidelines
- Coding Style Guide
- Contributor Platforms
- Stuff to read
- Extending Standard Library Specs
- Improve Gem Support in Rubinius
- Actors - Concurrent Rubinius
- FFI or Foreign Function Interface
