Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
tag: v2.1.0
Commits on Nov 7, 2010
  1. @dchelimsky

    bump to 2.1.0

    dchelimsky authored
  2. @dchelimsky

    history

    dchelimsky authored
  3. @dchelimsky

    eliminate some warnings

    dchelimsky authored
Commits on Nov 6, 2010
  1. @txus @dchelimsky

    Fix Marshal serialization of stubbed objects

    txus authored dchelimsky committed
    - Closes #27.
Commits on Oct 23, 2010
  1. @dchelimsky

    links to docs

    dchelimsky authored
Commits on Oct 22, 2010
  1. @dchelimsky
Commits on Oct 18, 2010
  1. @txus @dchelimsky

    15719 already fixed in stubbed_message_expectations_spec.rb

    txus authored dchelimsky committed
    - Closes #26.
  2. @dchelimsky

    update versions

    dchelimsky authored
Commits on Oct 11, 2010
  1. @dchelimsky
Commits on Oct 10, 2010
  1. @dchelimsky

    update rake tasks

    dchelimsky authored
  2. @dchelimsky

    prep for 2.0.0

    dchelimsky authored
  3. @dchelimsky

    reorg some features

    dchelimsky authored
  4. @dchelimsky

    rename feature dir

    dchelimsky authored
  5. @dchelimsky

    add a little relish

    dchelimsky authored
  6. @dchelimsky

    words

    dchelimsky authored
Commits on Oct 9, 2010
  1. @myronmarston @dchelimsky

    Allow specs to run on ruby 1.8.6.

    myronmarston authored dchelimsky committed
  2. @myronmarston @dchelimsky

    Added spec demonstrating mock return value for an edge case.

    myronmarston authored dchelimsky committed
    When a method has been stubbed previously to return a certain value (say, in a before(:each)), and then mocked w/o a return value (say, in a spec, to ensure a method was called), the stubbed value should still be returned.
Commits on Oct 5, 2010
  1. @dchelimsky

    bump version to 2.0.0.rc

    dchelimsky authored
  2. @dchelimsky

    update history

    dchelimsky authored
Commits on Oct 3, 2010
  1. @dchelimsky

    Raise with unexpected args message instead of NoMethodError when a stub

    dchelimsky authored
    is specified with args but received with different args.
Commits on Oct 2, 2010
  1. @dchelimsky
  2. @dchelimsky
  3. @myronmarston @dchelimsky

    Fixed YAML serialization of a stubbed object.

    myronmarston authored dchelimsky committed
    Previously, the mock proxy would be serialized when #to_yaml is called on a stubbed object.  The mock proxy includes a reference to a proc.  When the yaml string is deserialized with YAML.load, you'd get an "allocator undefined for Proc" TypeError.
    
    This fix prevents stubbing from setting any new instance variables on the stubbed object, so that the YAMl serialization is not affected.
  4. @dchelimsky
  5. @dchelimsky

    update history

    dchelimsky authored
  6. @nbraem @dchelimsky

    should pass block to expectation block

    nbraem authored dchelimsky committed
  7. @graaff @dchelimsky
Commits on Sep 28, 2010
  1. @myronmarston @dchelimsky

    Fixed YAML serialization of a stubbed object.

    myronmarston authored dchelimsky committed
    Previously, the mock proxy would be serialized when #to_yaml is called on a stubbed object.  The mock proxy includes a reference to a proc.  When the yaml string is deserialized with YAML.load, you'd get an "allocator undefined for Proc" TypeError.
    
    This fix prevents the mock proxy from being serialized, so that the object is serialized the same as it would if it hadn't been stubbed.
    
    Note that Marshaling also breaks when Marshal.dump is passed a stubbed object, with a "singleton can't be dumped" error.  I'm not yet sure how to fix this, so I've left a pending spec for it.
Commits on Sep 27, 2010
  1. @dchelimsky

    rename file

    dchelimsky authored
Commits on Sep 26, 2010
  1. @andersondias @dchelimsky

    Fixing typo

    andersondias authored dchelimsky committed
Commits on Sep 13, 2010
  1. @dchelimsky
  2. @dchelimsky
  3. @dchelimsky
Commits on Sep 12, 2010
  1. @dchelimsky
  2. @dchelimsky

    prep for beta.21

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