Project

General

Profile

Actions

Bug #896

closed

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

Added by okkez (okkez _) almost 13 years ago. Updated over 10 years ago.

Status:
Closed
Priority:
Normal
ruby -v:
Backport:
[ruby-core:20610]

Description

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


Files

minitest.diff (2.02 KB) minitest.diff okkez (okkez _), 12/17/2008 04:44 PM
Actions #1

Updated by yugui (Yuki Sonoda) almost 13 years ago

  • Target version set to 1.9.1 Release Candidate

=begin

=end

Actions #2

Updated by yugui (Yuki Sonoda) almost 13 years ago

  • Due date set to 12/24/2008

=begin

=end

Actions #3

Updated by zenspider (Ryan Davis) almost 13 years ago

  • 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

Actions

Also available in: Atom PDF