require “minitest/autorun” class MyModel def my_method; end end class TestRaiseException < MiniTest::Unit::TestCase def test_raise_exception model = MyModel.new raises_exception = -> { raise ArgumentError.new } model.stub :my_method, raises_exception do assert_raises(ArgumentError) { model.my_method } end end end
There is a Test::Unit “compatibility” module that comes with Minitest, so that you can (presumably) use your existing Test::Unit tests as-is. This is probably the Test::Unit module you are seeing. As of rails 3.2.3, generator-created tests include rails/test_help which includes test/unit. The test “something” do syntax is a rails extension. It’s defined in ActiveSupport::Testing::Declarative, which … Read more
TL;DR The most direct way to check this is to sort the arrays before checking their equality. json.map{|d| d[“id”]}.sort.must_equal Database.all.pluck(:id).sort Still here? Okay. Let’s talk about comparing elements in an array. As it is, the map{} is already somewhat irrelevant to the test and adding clutter, I’d prefer to not add even more. Well, that … Read more
MiniTest does implement assert_nothing_raised in its Test::Unit compatibility layer, but in its own tests (MiniTest::Unit and MiniTest::Spec) it does not implement any test like this. The reason is, the programmer argues, that testing for nothing raised is not a test of anything; you never expect anything to be raised in a test, except when you … Read more
In assert_select, you can also use a question mark for the attribute value, and then follow with a string to match. assert_select “a[href=?]”, “https://stackoverflow.com/desired_path/1” There’s another way to use assert_select that is more friendly, especially if you want to match a partial string or regexp pattern: assert_select “a”, :href => /acebook\.com\/share/
Minitest has a special .expect :call for checking if some method is called. describe SomeClass do it “should invoke right function” do mocked_method = MiniTest::Mock.new mocked_method.expect :call, return_value, [] some_instance = SomeClass.new some_instance.stub :right, mocked_method do some_instance.invoke_function(“right”) end mocked_method.verify end end Unfortunately this feature is not documented very well. I found about it from here: … Read more
I know several folks coming from RSpec to minitest struggling with the same question. They love the ability to nest using describe/context blocks and want to continue in minitest. There are several solutions: Use minitest’s spec DSL: While there are minor differences, the spec DSL gives you most (all?) of the good parts of the … Read more
There are setup() and teardown() methods available. The documentation also lists before() and after() as being available. Edit: Are you looking to run something before each test or before or after the whole suite is finished?
This question is similar to How to run all tests with minitest? Using Ruby 1.9.3 and Rake 0.9.2.2, given a directory layout like this: Rakefile lib/alpha.rb spec/alpha_spec.rb Here is what alpha_spec.rb might look like: require ‘minitest/spec’ require ‘minitest/autorun’ # arranges for minitest to run (in an exit handler, so it runs last) require ‘alpha’ describe … Read more
I’m one of the RSpec developers, and have never used minitest, so take my biases into account when reading this answer. By and large, RSpec’s power comes from the fact that it reifies so many testing concepts into first class objects. Where Test::Unit and Minitest use simple methods for making assertions, RSpec uses first-class matcher … Read more