minitest

In RSpec I could create helper modules in /spec/support/... module MyHelpers def help1 puts "hi" end end and include it in every spec like this: RSpec.configure do |config| config.include(MyHelpers) end and use it in my tests like this: describe User do it "does something" do help1 end end How can I include a module into all MiniTest tests without repeating myself in every test? minitest does not provide a way to include or extend a module into every test class in the same way RSpec does. Your best bet is going to be to re-open the test case class (differs, depending on the minitest version

After using RSpec for several projects, I'm giving minitest/unit a go. I'm liking it so far, but I miss using describe/context blocks to group my tests/specs in a logical way. I know minitest/spec provides this functionality, but I like that minitest/unit feels a bit closer to barebones Ruby. Are there any gems that provide describe/context support for minitest/unit? Or, should I just live with my long, unorganized test files in minitest/unit? 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

I am new to Ruby on Rails and testing. When I run rake test I get the following error: /Users/jarvis/.rvm/gems/ruby-1.9.2-p180@rails3tutorial/gems/rack-1.3.4/lib/rack/backports /uri/common_192.rb:53: warning: already initialized constant WFKV_ /Users/jarvis/.rvm/gems/ruby-1.9.2-p180@rails3tutorial/gems/turn-0.8.3/lib/turn/autorun /minitest.rb:14:in `<top (required)>': MiniTest v1.6.0 is out of date. (RuntimeError) `gem install minitest` and add `gem 'minitest' to you test helper. from /Users/jarvis/.rvm/gems/ruby-1.9.2-p180@rails3tutorial/gems/activesupport-3.1.1/lib /active_support

I would like to have unit tests output color in my dev environment. However, I can't make it work on Linux (Debian and Ubuntu). When I include the following libs: require 'minitest/autorun' require 'minitest/unit' require 'minitest/pride' I get: /usr/local/rvm/gems/ruby-1.9.2-p136/gems/minitest-2.3.1/lib/minitest/pride.rb:35:in `<top (required)>': undefined method `output' for MiniTest::Unit:Class (NoMethodError) caused by the code: MiniTest::Unit.output = PrideIO.new(MiniTest::Unit.output) I have seen a working Rspec variant . Unfortunately, my Ruby knowledge is not enough to see differences.

I have just watched a Railscast for Minitest. What are the pros and cons for using RSpec vs Minitest for testing a rails app? Which features will I lose converting from RSpec to Minitest? 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 objects that support negation, self-description and more. RSpec's examples

i would like to disable use_transactional_fixtures = false in ministest to catch after_commit callback. What and where should i set-up? You have a few options. One is to create a test without transactional fixtures and hope that the changes you make to the test database isn't going to break any other tests. class SomethingTest < ActiveSupport::TestCase self.use_transactional_fixtures = false def test_something_with_after_commit # do work here, which will change your test database end end Another option you have is to keep the transactional fixtures, but invoke the after_commit callback

I get URI::InvalidURIError testing Rails Home controller: require 'test_helper' class HomeControllerTest < ActionDispatch::IntegrationTest test "should get index" do get :index assert_response :success end end get the following error: E Error: HomeControllerTest#test_should_get_index: URI::InvalidURIError: bad URI(is not URI?): http://www.example.com:80index test/controllers/home_controller_test.rb:7:in `block in <class:HomeControllerTest>' The stack is the following: Rails 5.0.0.beta3 minitest (5.8.4) Controller tests inherit from ActionController::TestCase , while your test inherits from