Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP
branch: master
Commits on Nov 22, 2008
  1. @floehopper

    It seems that current thinking is that its better to publish gems to …

    floehopper authored
    …RubyForge, so I'm removing the gemspec and switching off gem building on GitHub.
  2. @floehopper
  3. @floehopper
  4. @floehopper
  5. @floehopper

    Sorted out requires so everything works with Ruby 1.8.6 & Ruby 1.9, b…

    floehopper authored
    …oth with and without minitest gem installed. I suspect things will break if you 'take over' Test::Unit with MiniUnit using the 'use_miniunit yes' command. MiniTestAdapterTest should not be run if MiniTest is not available, but it's worth a warning.
Commits on Nov 21, 2008
  1. @floehopper
  2. @floehopper

    Added MiniTest support thanks to sprsquish on GitHub. I added an acce…

    floehopper authored
    …ptance test for using MiniTest with Mocha. I removed the if/else logic so that you can use both Test::Unit or MiniTest TestCases with Mocha. I fixed a problem with the assertion counting in MiniTest. Currently this requires the MiniUnit gem to be installed and I have only tested it on Ruby 1.8.6 with MiniTest 1.3.0.
  3. @floehopper

    Fixed test case class name which was a duplicate of another test case…

    floehopper authored
    … and didn't match its file name.
Commits on Nov 19, 2008
  1. @floehopper
  2. @floehopper
Commits on Nov 16, 2008
  1. @sprsquish

    add support for minitest

    sprsquish authored
Commits on Nov 3, 2008
  1. Gem::manage_gems is deprecated.

    jamesmead authored
  2. Updated version to 0.9.2 and added release notes.

    jamesmead authored
  3. Patch [#22630] Fix for a bug in running Rails tests with Ruby 1.8.7. …

    jamesmead authored
    …Array#flatten was being called which in turn was checking whether each element responded to #to_ary. This check was using the two parameter version of #respond_to?, but Mock was only defining a one parameter version.
Commits on Oct 30, 2008
  1. Improved documentation to address [#22530] 'Mock methods with multipl…

    jamesmead authored
    …e return values not possible?'
Commits on Sep 11, 2008
  1. @floehopper
Commits on Aug 30, 2008
  1. @floehopper

    Add release notes for 0.9.1

    floehopper authored
  2. @floehopper
Commits on Aug 14, 2008
  1. @floehopper

    Fixed bug #21465 - expects & stubs should support method names as str…

    floehopper authored
    …ings (as well as symbols) or fail fast. Convert all expectation method names to a symbol in case they were supplied as a string.
  2. @floehopper

    Removed unused method.

    floehopper authored
  3. @floehopper

    By removing Mock#unexpected_method_called we reduce the number of met…

    floehopper authored
    …hods vulnerable to the problem that surfaced in bug #21563.
  4. @floehopper
  5. @floehopper

    Fix bug #21563 - stubbing 'verified?' method is unsafe. Instance meth…

    floehopper authored
    …od names on the Mock class should be more obscure.
Commits on Jul 24, 2008
  1. @floehopper
  2. @floehopper
Commits on Jul 17, 2008
  1. @floehopper
  2. @floehopper
  3. @floehopper

    Now that ClassMethod#method is a string in Ruby 1.8 and a symbol in R…

    floehopper authored
    …uby 1.9 we can simplify the implementation of all of the #method_exists? methods. These changes are also part of the speed improvements suggested by Chris McGrath.
  4. @floehopper

    It will make life easier if ClassMethod#method and #hidden_method are…

    floehopper authored
    … both symbols in Ruby 1.9, but strings in Ruby 1.8.
  5. @floehopper

    ClassMethod#method is normally a symbol, so it makes more sense if #h…

    floehopper authored
    …idden_method is also a symbol rather than a string.
  6. @floehopper
  7. @floehopper

    There is no point in running (potentially expensive) checks if config…

    floehopper authored
    …uration is set to allow such checks to fail. This is a relatively quick fix in response to Chris McGrath's performance problems. In the long run I suspect there is some duplication here that could be refactored away.
Commits on Jul 11, 2008
  1. @floehopper
Commits on Jul 3, 2008
  1. @floehopper
  2. @floehopper

    Fix bug #20883 - never should raise when called to prevent follow up …

    floehopper authored
    …errors. Fail fast when there are no matching invokable expectations and handle the stub_everything case sensibly. This might not be entirely backwards compatible, but I think the benefits outweigh the risks. The most likely change is that a test that was already failing will now fail faster, which doesn't seem so awful.
Something went wrong with that request. Please try again.