I'm running ruby 1.8.6. I installed the minitest 1.3.1 gem, which is the new defacto replacement for the Test::Unit framework in Ruby 1.9 The API is supposed to be the same. I wrote a small test to get things rolling require 'rubygems' gem 'minitest' require 'minitest/unit' MiniTest::Unit.autorun class CategoryMiniTest < MiniTest::U...
A two-parter with a quick intro. Intro: I'm coming to Ruby from Perl, and I'm a bit lost among the test framework choices. I understand that there is probably no single, all-around best choice, but I can't even get a clear picture of the playing field. So, first, MiniTest or Test::Unit? I just realized that 1.9.1 defaults to MiniTest no...
With test/unit, and minitest, is it possible to fail any test that doesn't contain an assertion, or would monkey-patching be required (for example, checking if the assertion count increased after each test was executed)? Background: I shouldn't write unit tests without assertions - at a minimum, I should use assert_nothing_raised if I'm...
The spec library in Minitest is great. I've been able to use it within Rails unit tests no problem. However, Rails functional test inherit from ActionController::TestCase which provides instance variables like @controller in it's setup. Has anyone been using the Minitest::Spec lib for their Rails functional tests? If not, I'm conside...