The default unit testing framework for Ruby as of Ruby 1.9.x is the very capable MiniTest. Read on to find out how to use it best to your advantage.
Ever since Ruby Version Manager was released, it's been the de facto standard for installing Ruby.
The following is a tutorial on creating a URL Shortener service (a la TinyURL.com or bit.ly) in Ruby on Rails 3. It covers developing the application, integrating a style and deploying to Heroku.
The default unit testing framework for Ruby as of Ruby 1.9.x is the very capable MiniTest. Read on to find out how to use it best to your advantage.
While assertions are just fine, MiniTest also provides an RSpec-like interface for doing spec statements. For example, instead of saying assert_empty a, you can simply say a.must_be_empty. While this sounds like a small difference, it's much more readable. And it shows off a bunch of Ruby internal voodoo that most other languages just aren't capable of doing. And how can that be a bad thing?
Like Test::Unit, MiniTest provides a small library of assertions for you to use. While you can just cram any statement into assert or refute, it's much more readable to use some of the other assertion methods, such as assert_empty or assert_respond_to.
MiniTest replaced Test::Unit in the Ruby standard library as of Ruby 1.9.x. And while it is (mostly) a drop-in replacement for Test::Unit, there are some differences and improvements. First up, the basic assertions.