Getting Rails Test Suite Running on JRuby
This post is about Issue #11700 - Getting Rails Test Suite to run on Rails. Incase you don’t have time to read the full post, see the following presentation.
You are a ruby developer & want to run rails on anything other than CRuby/MRI which is the de-facto ruby implementation written in C. Reasons could the that you are having problems with GC, need fully multi-threaded env(no GVL/GIL) or you just curious like me. so, you research a bit & find that there is this thing called JRuby which is implemntation of ruby programming language that runs of battle-tested & rock solid JVM. JVM is the same VM which is used by Java & all other JVM based languages like scala, closure, JPython etc.
You liked JRuby
lets assume you tried JRuby on Devloplement machine & liked JRuby because:
- You need for specific Java libraries & JRuby Allows you to call any Java library from ruby.
- want to real Concurrency, not GVL/GIL contrainted provided by CRuby/MRI.
- Better GC which helps with long running processes
- Better Performance
So next question you ask is:
Does Rails support JRuby?
Yes. Rails runs on JRuby out of the box but its on different Level of support that rails test suite fails to run, it fails. Current status is allowed failures
We consider any bugs on JRuby to be real bugs that need fixed, we just don’t actively run the test suite against JRuby – Steve Kalbnik (Rails Core Committor) on #11700
But as rails is open-source, which means you can help to get test suite running. Pull Request are welcome.
How to Run Rails Test Suite on JRuby
Grab Rails Code:
$ git clone http://github.com/rails/rails.git
Switch to JRuby
$ rvm use jruby #if using rvm $ ruby -v ruby 1.7.12 (1.9.3p392) 2014-04-15 643e292 on Java HotSpot(TM) 64-Bit Server VM 1.7.0_51-b13 [darwin-x86_64]
$ cd /path/to/rails/checkout $ bundle install
Run Tests on particular component.
To run tests only for particular component(ActionPack, ActiveRecord, etc.). All you need to do is to cd into that component directory & run
rake test. For example, run
ActiveSupport tests you can:
$ cd activesupport $ rake test
Run a particular test
$ cd activesupport $ ruby -vIlib:test --client test/multibyte_chars_test.rb ruby 1.7.12 (1.9.3p392) 2014-04-15 643e292 on Java HotSpot(TM) 64-Bit Server VM 1.7.0_51-b13 [darwin-x86_64] /Users/gaurish/.rvm/gems/jruby-1.7.12@rails-dev/gems/minitest-5.3.3/ lib/minitest.rb:46 warning: (...) interpreted as grouped expression Run options: --seed 21522 # Running: lib/rational.rb is deprecated ......................................................................... ..............F.... Finished in 1.735000s, 53.0259 runs/s, 195.3890 assertions/s. 1) Failure: MultibyteCharsExtrasTest#test_tidy_bytes_should_tidy_bytes [test/multibyte_chars_test.rb:657]: --- expected +++ actual @@ -1 +1 @@ -"a€a" +#<ActiveSupport::Multibyte::Chars:0xXXXXXX @wrapped_string="€a"> 92 runs, 339 assertions, 1 failures, 0 errors, 0 skips
Okay, so now you have found a failing test. now, get this to green & submit a Pull Request. And please don’t forget to mention issue #11700 in your PR, so everyone can track it that you are working on the changes.
For more info, please see: