Panasonic Youth rob sanheim writes about software, business, ruby, music, stuff and things

Did redgreen get borked?

I recently had to reinstall all my favorite gems and tools on a powerbook, and desired colored test goodness. So after bringing in redgreen and zentest gems, amongst others, I saw the following:

rob@fixx:~/src/relevance/pharminst/trunk$ rake|redgreen
-bash: redgreen: command not found
^Crake aborted!

rob@fixx:~/src/relevance/pharminst/trunk$ rake|rg
/opt/local/lib/ruby/gems/1.8/gems/redgreen-1.2.2/bin/rg:6: can't convert nil into String (TypeError)
        from /opt/local/bin/rg:16:in `load'
        from /opt/local/bin/rg:16
^Crake aborted!

On looking at the code, I see that the command line filter was renamed to ‘rg’, only now it just throws that error see above if i filter a test run through it. Doing a ‘require redgreen’ in my autotest file (.autotest) still works, sort of, as its just the seperator bar that gets colored and not the actual assertion line.

Did I mess something up on install, or has anyone else noticed this?

Try this in your .autotest file

require ‘redgreen/autotest’

Thanks gordon, that at least fixes autotest. Now to figure out how to run a standard rake task through it..

The ‘redgreen’ gem can be used with rake by putting a “require ‘redgreen’” in your test_helper.rb. This also causes it to work with single *_test.rb files. Assuming Rails, of course. Otherwise you can us the ‘rg’ runner — $ rg my_test_file.rb