testunit

I have test-unit installed and rspec installed (along with -core , -expectations , -mocks and -rails version 2.6.x). When I run the command rails new foo , it uses test-unit to generate the test stub files instead of rspec . Is there an option where I can tell rails to use rspec to generate the tests instead? The following should work: at command line: rails new MYAPP -T # The -T option tells rails not to include Test::Unit in Gemfile: gem 'rspec-rails' at command line: bundle install rails g rspec:install Create your new rails application as: rails new <app_name> -T Or remove your test

I want to stub a method with Mocha only when a specific parameter value is given and call the original method when any other value is given. When I do it like this: MyClass.any_instance.stubs(:show?).with(:wanne_show).returns(true) I get an unexpected invocation for MyClass.show?(:other_value) I also know, that I can stub all parameters when writing the mock without the ´with´-call and then give my specific mock. But then I have to know the return value for every call, which is not the case :/ tldr; Is there a way to call the original method in a stub or to stub just specific parameters and

I read somewhere that 'minitest' is the "new test::unit for ruby 1.9.2+". But ruby 1.9.3 seems to include both test::unit and minitest , is that true? In the default rails testing, as outlined in the Rails testing guide .... things like ActiveSupport::TestCase , ActionController::TestCase , are these using Test::Unit or Minitest ? In the rails guide, it shows examples with tests defined like this: test "should show post" do get :show, :id => @post.id assert_response :success end That syntax, test string , as opposed to defining methods with names like test_something -- isn't mentioned in the

For example, when these tests are run, I want to ensure that test_fizz always runs first. require 'test/unit' class FooTest < Test::Unit::TestCase def test_fizz puts "Running fizz" assert true end def test_bar puts "Running bar" assert true end end Update : Why do I want to do this? My thought is that early failure by certain tests (those testing the simpler, more fundamental methods) will make it easier to track down problems in the system. For example, the success of bar hinges on fizz working correctly. If fizz is broken, I want to know that right off the bat, because there's no need to

I have a unit test (example is modified Test::Unit documentation ) require 'test/unit' class TC_MyTest < Test::Unit::TestCase def test_something assert(true) end end When I execute it, I get: Loaded suite C:/test Started . Finished in 0.0 seconds. 1 tests, 1 assertions, 0 failures, 0 errors I would like to get something like this ( test_something is outputted): Loaded suite C:/test Started test_something . Finished in 0.0 seconds. 1 tests, 1 assertions, 0 failures, 0 errors If you're testing in rails you can use rake test TESTOPTS=-v Run unit test with verbose option. test.rb -v v or test.rb -