MiniTest::Assertions#assert_match arguments order is different from Test::Unit::Assertions::assert_match
I write a simple patch same as 'test/unit'.
more details to see test code of 'test/unit'.
Updated by zenspider (Ryan Davis) over 13 years ago
- Status changed from Open to Closed
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.