Bug #896

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

Added by okkez _ about 3 years ago. Updated 10 months ago.

[ruby-core:20610]
Status:Closed Start date:12/17/2008
Priority:Normal Due date:12/24/2008
Assignee:Ryan Davis % Done:

0%
Category:lib
Target version:1.9.1 Release Candidate
ruby -v:

Description

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

minitest.diff (2 kB) okkez _, 12/17/2008 04:44 pm

History

#1
Updated by Yuki Sonoda about 3 years ago

  • Target version set to 1.9.1 Release Candidate

#2
Updated by Yuki Sonoda about 3 years ago

  • Due date set to 12/24/2008

#3
Updated by Ryan Davis about 3 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.

Also available in: Atom PDF