Skip to content
This repository

Dec 26, 2013

  1. Brian Shirai

    Removed ruby_version_is guards from Array specs.

    brixen authored

Apr 15, 2013

  1. Kenichi Kamiya

    Fix spec instance~class matchers for Array#reverse

    kachick authored

Dec 09, 2010

  1. Paul Mucur

    Add coverage for 1.9.3 rb_ary_dup behaviour as of r30148 [ruby-core:3…

    …3640]
    
    This affects Array#sort, #reject, #transpose, #uniq, #compact and #shuffle.
    mudge authored

Feb 22, 2010

  1. Brian Shirai

    Standardize require lines.

    Since 1.8 does not canonicalize the filename that is required,
    the same file can be required multiple time. This is particularly
    true for spec_helper.rb, however it could also affect execution
    of the specs. On 1.9, the path is canonicalized. Using
    File.expand_path should eliminate this difference on 1.8 and 1.9.
    brixen authored

Jan 05, 2010

  1. Hiro Asari

    Avoid result.class.should == Class

    BanzaiMan authored

Jul 01, 2009

  1. Eloy Durán

    Encoding#find coerces object with #to_str.

    Various style fixes.
    alloy authored

May 03, 2009

  1. Thiago Pradi

    Array Core libs specs ported to Ruby 1.9

    Signed-off-by: Brian Ford <bford@engineyard.com>
    tchandy authored brixen committed

Feb 10, 2009

  1. Brian Shirai

    Fixed use of guards in the specs.

    See http://rubyspec.org/wiki/rubyspec/Guards for the correct use
    of all the guards. In particular, note that the compliant_on/
    not_compliant_on guarded specs will always run on MRI. The
    deviates_on, extended_on, and not_supported_on never run on MRI.
    These latter three guards will now raise an exception if passed
    :ruby. Also, platforms like :windows are not proper for any of
    these implementation compliance guards.
    
    Use ruby_version_is or ruby_bug guards for version-specific specs
    or specs that expose bugs in MRI.
    brixen authored

Dec 29, 2008

  1. Brian Shirai

    Removed separate 1.8 directory and moved specs up.

    brixen authored
Something went wrong with that request. Please try again.