why.markdown

• Why I need to rename stuff (again) when moving from minitest 4 to minitest 5?
• Why a 0.x upgrade of ActiveRecord forces my project to minitest 5 even though my project is on 4?
• Why Rake runs the autorunner for every thread I start within my rake task that has nothing to do with minitest?
• Why there is no "around wrapper" for every test method that is published, and if there is why did it's API had to change between 4 and 5?
• When I require "test/unit" because somethign in my project wants to have Test::Unit, is that really necessary?
• Who is responsible/maintaining the test task that is supplied in Rake?

• Because I changed the namespace. Once. On a major release, after 7 years of staying on the previous one. "Again"? No:

% ls | wc -l
      95
% egrep -hir "^module.minitest$" [1234]*/lib | occur
120: module MiniTest
% egrep -hir "^module.minitest$" [5]*/lib | occur
192: module Minitest

95 releases and I've changed the namespace once.

• I don't maintain rails. Why are you asking me? How about you ask them?
• I don't maintain rake. Why are you asking me? How about you ask them?
• I have no idea what you're talking about. There is a minitest-around gem. Ask them.
• Minitest != test/unit. If you want to use test/unit, use it. If you want to use minitest, don't use test/unit.
• Again, I don't maintain rake. Why are you asking me? How about you ask them?

Do my answers sound unreasonable to you? Well, the questions are unreasonable, IMO. 6 "questions" and only 2 of them are marginally related to minitest. Maybe you should stay on rspec. I really don't have time for this.