This reminds me of some code I worked on in Heretix. We did the same thing for Ruby strings.. though it had a few quirks.

Now we have a nice packaged gem! Thanks.

I had made something very similar myself for personal use. Very cool stuff. Any chance we can get this working with zentest?

PS: Just noticed the example as i’m watching battlestar galactica… hrm. ponderous, indeed. :)

Anyone have this problem?

Local gem file not found: color*.gem Attempting remote installation of ‘color’ Updating Gem source index for: require.errtheblog.com ERROR: While executing gem … (TypeError) can’t convert Hash into String

“screencast” – you are so web2.0. :)

Of course, there’s already the Text::Highlight gem. But that’s no fun.

Win32Console is already gemified – just install win32console. No need to go to another gem repository.

It’s a different project than Gonzales, but uses his code:

http://rubyforge.org/projects/winconsole/

autotest can use the redgreen gem to do this…

1. in ~/.autotest require ‘autotest/redgreen’

Textile mangled my code…

Anyway, there is already a color gem. Maybe a different name could be used?

http://rubyforge.org/projects/color/

Hope this will be of some use.

I wrote up some code to colorize your test suite that is run by rake. I wanted to run all my test and have the output be colorized without much work, so rather than hacking the ruby test libs I just re-opened them a little.

Here is the url: http://www.nkryptic.com/2006/10/26/rails-colorized-rake-testing

For irb-specific coloring, check out http://pablotron.org/software/wirble/

FYI, in the States, “colored” can be a charged term, so beware.

Yes, beware, I as a computer know of such prejudices of color. Deep Blue? I’m actually quite cheery and my aluminum and silicon parts are neither deep, nor blue.

In the screenshot it still says gem install color and require colo@r. To get it working change both to @colored

I failed to get it working with Windows too, but after 20 minutes of inspecting how redgreen works, I could get it to work. My solution doesn’t require any external gems or plugins, but it does pollute your test_helper even more. Maybe I should convert it to plugin some day and take use of redgreen.

1. Hack for colorifying rake tests – green tests are now really green!
2. (most stuff shamelessly stolen from redgreen.rb)

if ENV[‘COLORIZE’] || ENV[‘TERM’] == ‘linux’ require ‘test/unit’ require ‘test/unit/ui/console/testrunner’ end

module Color
  COLORS = { :clear => 0, :red => 31, :green => 32, :yellow => 33 }
  def self.method_missing(color_name, *args)
    colname = color_name.to_s
    ansi_color = (colname =~ /^light/ ?
                  light_color(colname.gsub(/light/, '')) :
                  color(colname))
    ansi_color + args.first + color(:clear)
  end
  def self.color(color)
    "\e[#{COLORS[color.to_sym]}m"
  end
end

def self.light_color(color)
  "\e[1;#{COLORS[color.to_sym]}m"
end

class Test::Unit::UI::Console::TestRunner
  def adjust_io_fd
    if !@io_set && PLATFORM =~ /win32/
      @io_set = true
      require 'Win32/Console/ANSI'
      @io = Win32::Console::ANSI::IO.new
    end
  end
end

def output_single(something, level=NORMAL)
  return unless (output?(level))
  adjust_io_fd
  something = case something
              when '.' then Color.lightgreen('.')
              when 'F' then Color.lightred("F")
              when 'E' then Color.lightyellow("E")
              else something
              end
  @io.write(something)
  @io.flush
end

class Test::Unit::TestResult
  alias :old_to_s :to_s
  def to_s
    if old_to_s =~ /\d+ tests, \d+ assertions, (\d+) failures, (\d+) errors/
      Color.send($1.to_i != 0 || $2.to_i != 0 ? :lightred : :lightgreen, $&)
    end
  end
end

class Test::Unit::Failure
  alias :old_long_display :long_display
  def long_display
    old_long_display.sub('Failure', Color.lightred('Failure'))
  end
end

class Test::Unit::Error
  alias :old_long_display :long_display
  def long_display
    old_long_display.sub('Error', Color.lightyellow('Error'))
  end
end