Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
branch: master
Commits on Jun 24, 2010
Commits on May 26, 2010
  1. @qrush
  2. @qrush

    Updating gemspec

    qrush authored
  3. @qrush

    Fixed spies passing with too many invocations

    authored qrush committed
  4. @qrush

    Fixed a bug with have_received/assert_received on pure mocks

    authored qrush committed
  5. @qrush

    Added docs for assert_received/have_received

    authored qrush committed
  6. @qrush

    Added failure messages to assert_received/have_received

    authored qrush committed
  7. @qrush

    Added an RSpec matcher for spies

    authored qrush committed
  8. @qrush

    Implented invocation count checking for spies

    authored qrush committed
  9. @qrush

    Fixed assert_received to restrict matches to the correct mock

    authored qrush committed
  10. @qrush

    Added spy matching for arguments

    authored qrush committed
  11. @qrush

    Added a basic implementation of test spies

    authored qrush committed
  12. @qrush

    Ignoring some development files

    authored qrush committed
Commits on May 15, 2010
  1. @floehopper

    Fix test incorrectly failing under Rubinius 1.0.

    floehopper authored
    This test imposed too many constraints. It appears that
    Object#inspect legitimately calls Object#object_id in Rubinius.
    But we're only interested in what 'id' methods
    Mocha::ObjectMethods#mocha_inspect calls. By stubbing
    Object#inspect we can relax the constraints imposed by the test.
Commits on May 13, 2010
  1. @floehopper

    Improve documentation for Expectation#raises.

    floehopper authored
    I've had a number of people suggesting an extension to the API
    to cope with custom exceptions that have extra constructor
    parameters. However, since Mocha just passes the arguments on
    to Kernel#raise, it's possible to pass in an instance of an
    exception. Thus no change to the API is required, but it does
    seem worthwhile pointing this out in the docs.
Commits on May 12, 2010
  1. @floehopper

    Fix for Ruby 1.9.2.

    floehopper authored
    It appears that it is no longer possible to subvert the protection
    of a method by calling it via send in Ruby 1.9.2.
  2. @floehopper
  3. @alloy @floehopper

    Hacked on James's MiniTest TestResult code to make the acceptance tes…

    alloy authored floehopper committed
    …ts run on 1.9 HEAD.
    
    There are still 4 failures because for some reason the backtrace line numbers
    are off by one. And the minitest_test test case does not run when the whole
    suite is ran with MiniTest, still need to look into that.
  4. @alloy @floehopper

    Made the unit tests run on 1.9.2dev r25249.

    alloy authored floehopper committed
  5. @floehopper
  6. @floehopper
  7. @floehopper

    Add patches for different versions of Test::Unit.

    floehopper authored
    Because Mocha effectively replaces the Test::Unit::TestCase#run
    method, we need to ensure that any changes to the Test::Unit version
    of this method are reflected in the Mocha patches. This has been
    neglected since version 2.0.2.
    
    Also added warnings to aid debugging. These currently use
    Kernel#warn and therefore go to stderr. We may need to change this
    to make it easier to disable e.g. using the existing Mocha Logger.
    
    Also add a warning if an "unverified" version of Test::Unit is
    being used. And a warning if no suitable patch can be identified.
  8. @floehopper
  9. @floehopper

    Add patches for different versions of the MiniTest gem.

    floehopper authored
    Because Mocha effectively replaces the MiniTest::Unit::TestCase#run
    method, we need to ensure that any changes to the MiniTest version
    of this method are reflected in the Mocha patches. This has been
    neglected since version 1.3.1.
    
    Also added warnings to aid debugging. These currently use
    Kernel#warn and therefore go to stderr. We may need to change this
    to make it easier to disable e.g. using the existing Mocha Logger.
Commits on Feb 20, 2010
  1. @lukeredpath @floehopper
  2. @lukeredpath @floehopper
  3. @lukeredpath @floehopper

    Allow the creation of any/all composite matchers using & | semantics.

    lukeredpath authored floehopper committed
    This provides an alternative syntax for expecting any or all matchers to
    pass, e.g. foo.expects(:bar).with(equals(1) | equals(2)).
Commits on Sep 18, 2009
  1. @floehopper
  2. @floehopper

    Fixed Rails plugin which stopped working after 0.9.6. Updated documen…

    floehopper authored
    …tation to reflect this fix. Updated release notes and bumped version in preparation for release 0.9.8.
Commits on Sep 15, 2009
  1. @floehopper
  2. @floehopper

    The regexp_matches matcher won't match or raise an error on empty arg…

    Sander Hartlage authored floehopper committed
    …uments or arguments that don't respond to #=~
    
    Signed-off-by: James Mead <james@floehopper.org>
  3. @floehopper

    The includes matcher won't match or raise an error on empty arguments…

    Sander Hartlage authored floehopper committed
    … or arguments that don't respond to #include?
    
    Signed-off-by: James Mead <james@floehopper.org>
  4. @floehopper

    Now the has_value matcher won't match or raise error on empty argumen…

    Sander Hartlage authored floehopper committed
    …ts or arguments that don't respond to #values
    
    Signed-off-by: James Mead <james@floehopper.org>
  5. @floehopper

    Now the has_key matcher will not raise an error on empty arguments or…

    Sander Hartlage authored floehopper committed
    … arguments that don't respond to #keys, nor will it match
    
    Signed-off-by: James Mead <james@floehopper.org>
  6. @dan-manges @floehopper

    allow passing a block to Mocha::Configuration methods to only change …

    dan-manges authored floehopper committed
    …config for the duration of the block
    
    Signed-off-by: James Mead <james@floehopper.org>
Something went wrong with that request. Please try again.