Just a reminder for those of you making contributions. If you are changing JRuby code, you should also try to run it against the Rubicon suite of tests (from the "rubytests" project at Rubyforge...use the CVS version). This test suite does not run 100%, but it does contain a large number of unit tests that should pass in JRuby. Compare multiple runs before and after your changes to confirm there are no regressions. There are a few tests that fail on and off, so try to run several times.
And of course, there are some apps that are good for testing particular areas as well:
- "jirb" is good for ensuring that bindings are working ok
- Rails' generate script is good for confirming multiple issues with modifying class defs, but only works on my cnutter_work1 branch right now
- you may find others...please add to this list
Finally, if you're looking for something to work on, there's a whole suite of tests in C Ruby's src, under the test dir. Pick a test and run it...it probably will have a few failures. These tests haven't been the greatest for confirming low-level language behavior, but they often illustrate peculiar edge-cases that should also work.
Rubicon is at:
http://rubyforge.org/projects/rubytests/
--
Charles Oliver Nutter @ headius.blogspot.com
JRuby Developer @ jruby.sourceforge.net
Application Architect @ www.ventera.com
