Bug #896: MiniTest::Assertions#assert_match arguments order is different from Test::Unit::Assertions::assert_match

• Status: Closed
• Assignee: zenspider (Ryan Davis)
• Target version: 1.9.1 Release Candidate

[okkez (okkez _)]

=begin
I write a simple patch same as 'test/unit'.
more details to see test code of 'test/unit'.
=end

[yugui (Yuki Sonoda)]

• Target version set to 1.9.1 Release Candidate

=begin

=end

[yugui (Yuki Sonoda)]

• Due date set to 12/24/2008

=begin

=end

[zenspider (Ryan Davis)]

• Status changed from Open to Closed

=begin
Argument order fixed. Sorry.

I left in respond_to check for ~= and non-forcing of Regexp.new. This allows assert_match to be used with custom objects that define =~. Not everything should be text oriented for assert_match.

Also fixed refute_match and made it act the same wrt respond_to etc.
=end