Permalink
Commits on Jun 21, 2010
  1. Use rdoc extension to encourage GitHub to use correct formatting.

    Thanks to a suggestion from Rohit Arondekar (rohit).
    floehopper committed Jun 21, 2010
Commits on Jun 11, 2010
Commits on Jun 5, 2010
  1. Only warn when the new 'debug' MOCHA_OPTION is supplied.

    I've added various debug warning statement in recent commits, but these should not be enabled by default. Also we now need to deal with multiple MOCHA_OPTIONS which should be supplied in a comma-delimited list.
    floehopper committed Jun 5, 2010
  2. Fix exception when running rake without test-unit gem.

    When test-unit gem >=v2.0.0 was installed but the "use_test_unit_gem" MOCHA_OPTION was not specified, a "comparison of Fixnum with Hash failed" exception was being raised when running the performance tests. This was because bits of the test-unit gem were being loaded accidentally and a Hash was being incorrectly supplied to the TestRunner.run method.
    floehopper committed Jun 5, 2010
  3. Mocha should not load bits of the test-unit gem by accident.

    This is an attempt at a fix for the problem that James Adam reported [1]. By using 'load' instead of 'require' to detect the version of Test::Unit, it seems like we can avoid rubygems trying to load bits of the test-unit gem when it's not wanted.
    
    [1] http://floehopper.lighthouseapp.com/projects/22289-mocha/tickets/50#ticket-50-13
    floehopper committed Jun 5, 2010
Commits on Jun 4, 2010
Commits on May 15, 2010
  1. Fix test incorrectly failing under Rubinius 1.0.

    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.
    floehopper committed May 15, 2010
Commits on May 13, 2010
  1. Improve documentation for Expectation#raises.

    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.
    floehopper committed May 13, 2010
Commits on May 12, 2010
  1. Fix for Ruby 1.9.2.

    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.
    floehopper committed May 11, 2010
  2. Hacked on James's MiniTest TestResult code to make the acceptance tes…

    …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.
    alloy committed with floehopper Oct 11, 2009
  3. Add patches for different versions of Test::Unit.

    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.
    floehopper committed May 12, 2010
  4. Add patches for different versions of the MiniTest gem.

    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.
    floehopper committed May 12, 2010
Commits on Feb 20, 2010
  1. Allow the creation of any/all composite matchers using & | semantics.

    This provides an alternative syntax for expecting any or all matchers to
    pass, e.g. foo.expects(:bar).with(equals(1) | equals(2)).
    lukeredpath committed with floehopper Feb 18, 2010
Commits on Sep 18, 2009
  1. Fixed Rails plugin which stopped working after 0.9.6. Updated documen…

    …tation to reflect this fix. Updated release notes and bumped version in preparation for release 0.9.8.
    floehopper committed Sep 18, 2009
Commits on Sep 15, 2009
  1. The regexp_matches matcher won't match or raise an error on empty arg…

    …uments or arguments that don't respond to #=~
    
    Signed-off-by: James Mead <james@floehopper.org>
    Sander Hartlage committed with floehopper Jul 8, 2009
  2. The includes matcher won't match or raise an error on empty arguments…

    … or arguments that don't respond to #include?
    
    Signed-off-by: James Mead <james@floehopper.org>
    Sander Hartlage committed with floehopper Jul 8, 2009
  3. Now the has_value matcher won't match or raise error on empty argumen…

    …ts or arguments that don't respond to #values
    
    Signed-off-by: James Mead <james@floehopper.org>
    Sander Hartlage committed with floehopper Jul 8, 2009
  4. Now the has_key matcher will not raise an error on empty arguments or…

    … arguments that don't respond to #keys, nor will it match
    
    Signed-off-by: James Mead <james@floehopper.org>
    Sander Hartlage committed with floehopper Jul 8, 2009
  5. allow passing a block to Mocha::Configuration methods to only change …

    …config for the duration of the block
    
    Signed-off-by: James Mead <james@floehopper.org>
    dan-manges committed with floehopper Jul 28, 2009
  6. Remove rdoc template incorporating google analytics from source contr…

    …ol. The file just needs to exist locally and be ignored by source control. This should stop the warning showing up on e.g. RunCodeRun build results.
    floehopper committed Sep 15, 2009
Commits on Jul 24, 2009
  1. The RDoc template incorporating Google Analytics isn't distributed in…

    … the gem (because it is only used when publishing the RDoc to Rubyforge), so we should ensure that the rdoc rake task still works when the custom template is not available. See http://floehopper.lighthouseapp.com/projects/22289/tickets/51.
    floehopper committed Jul 24, 2009
Commits on Jul 1, 2009
  1. Prepare for 0.9.7 release.

    floehopper committed Jul 1, 2009