From: "zzak (Zachary Scott)" Date: 2013-10-16T00:13:07+09:00 Subject: [ruby-core:57878] [ruby-trunk - Bug #8975] Confusing code sample for assert_send Issue #8975 has been updated by zzak (Zachary Scott). Please see #8778 for reference. To answer your question, lib/test (test/unit) is a legacy shim. I don't think documenting minitest advantages will help, because minitest may not stay in the stdlib forever. We could mention other libraries, including the full TU2 gem for those looking to upgrade. I think the natural progression is TU -> TU2, not TU -> MT ---------------------------------------- Bug #8975: Confusing code sample for assert_send https://bugs.ruby-lang.org/issues/8975#change-42474 Author: agrimm (Andrew Grimm) Status: Assigned Priority: Normal Assignee: zzak (Zachary Scott) Category: doc Target version: ruby -v: ruby 2.0.0p247 (2013-06-27 revision 41674) [x86_64-linux] Backport: 1.9.3: UNKNOWN, 2.0.0: UNKNOWN Test::Unit::Assertsions#assert_send has the code sample assert_send([[1, 2], :member?, 1]) # -> pass assert_send([[1, 2], :member?, 4]) # -> fail Having an array within an array is somewhat confusing. When I first read it, I ignored the extra square brackets. A less confusing example would be assert_send(["Hello world", :include?, "Hello"]) # -> pass assert_send(["Hello world", :include?, "Goodbye"]) # -> fail -- http://bugs.ruby-lang.org/