Skip to content
This repository

Mar 16, 2012

  1. John Firebaugh

    Add String#chop specs

    jfirebaugh authored brixen committed

Apr 14, 2011

  1. Brian Shirai

    Finally cleaned up trailing whitespace in spec files.

    brixen authored brixen committed

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

Feb 11, 2010

  1. Brian Shirai

    Made String#chop spec encoding agnostic.

    brixen authored

Feb 09, 2010

  1. Brian Shirai

    Do not use 1.9.2 in version strings.

    Notes:
    * Do NOT add ruby_bug guards for issues with 1.9. RubySpec specs
      only the behavior of 1.9 HEAD until 1.9.2 is officially released.
    brixen authored

Jan 05, 2010

  1. Hiro Asari

    Avoid result.class.should == Class

    BanzaiMan authored

Jun 05, 2009

  1. runpaint

    String#chop: Removed debug statement. (Mine ;-))

    runpaint authored

Jun 03, 2009

  1. runpaint

    String#chop: Fix 1.9 "invalid byte sequence" error

    The previous example used UTF-8 implicitly, which confused 1.9 because it was
    using a default encoding of ASCII. This caused an "invalid byte sequence"
    error on 1.9 when we used String#chop, which works with characters, not bytes.
    Explicitly encoding the string in UTF-8 for that example resolved the error.
    runpaint authored

Jun 02, 2009

  1. runpaint

    String#chop!: Guarded frozen behav. [core:23666]

    runpaint authored

Jun 01, 2009

  1. runpaint

    String: 1.9 methods raise RuntimeError when frozen

    runpaint authored

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.