Bug #896
closed
MiniTest::Assertions#assert_match arguments order is different from Test::Unit::Assertions::assert_match
Added by okkez (okkez _) over 15 years ago.
Updated about 13 years ago.
Description
=begin
I write a simple patch same as 'test/unit'.
more details to see test code of 'test/unit'.
=end
Files
- Target version set to 1.9.1 Release Candidate
- Due date set to 12/24/2008
- 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
Also available in: Atom
PDF
Like0
Like0Like0Like0