https://redmine.ruby-lang.org/https://redmine.ruby-lang.org/favicon.ico?17113305112008-12-20T21:19:25ZRuby Issue Tracking SystemRuby master - Bug #896: MiniTest::Assertions#assert_match arguments order is different from Test::Unit::Assertions::assert_matchhttps://redmine.ruby-lang.org/issues/896?journal_id=21632008-12-20T21:19:25Zyugui (Yuki Sonoda)yugui@yugui.jp
<ul><li><strong>Target version</strong> set to <i>1.9.1 Release Candidate</i></li></ul><p>=begin</p>
<p>=end</p> Ruby master - Bug #896: MiniTest::Assertions#assert_match arguments order is different from Test::Unit::Assertions::assert_matchhttps://redmine.ruby-lang.org/issues/896?journal_id=21732008-12-21T00:04:52Zyugui (Yuki Sonoda)yugui@yugui.jp
<ul><li><strong>Due date</strong> set to <i>12/24/2008</i></li></ul><p>=begin</p>
<p>=end</p> Ruby master - Bug #896: MiniTest::Assertions#assert_match arguments order is different from Test::Unit::Assertions::assert_matchhttps://redmine.ruby-lang.org/issues/896?journal_id=23762008-12-28T05:22:35Zzenspider (Ryan Davis)
<ul><li><strong>Status</strong> changed from <i>Open</i> to <i>Closed</i></li></ul><p>=begin<br>
Argument order fixed. Sorry.</p>
<p>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.</p>
<p>Also fixed refute_match and made it act the same wrt respond_to etc.<br>
=end</p>