Commits on Nov 22, 2008
  1. It seems that current thinking is that its better to publish gems to …

    …RubyForge, so I'm removing the gemspec and switching off gem building on GitHub.
    floehopper committed Nov 22, 2008
  2. Sorted out requires so everything works with Ruby 1.8.6 & Ruby 1.9, b…

    …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.
    floehopper committed Nov 22, 2008
Commits on Nov 21, 2008
  1. Added MiniTest support thanks to sprsquish on GitHub. I added an acce…

    …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.
    floehopper committed Nov 21, 2008
  2. Fixed test case class name which was a duplicate of another test case…

    … and didn't match its file name.
    floehopper committed Nov 21, 2008
Commits on Nov 19, 2008
Commits on Nov 16, 2008
  1. add support for minitest

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

    jamesmead committed Nov 3, 2008
  2. Updated version to 0.9.2 and added release notes.

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

    …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.
    jamesmead committed Nov 3, 2008
Commits on Oct 30, 2008
  1. Improved documentation to address [#22530] 'Mock methods with multipl…

    …e return values not possible?'
    jamesmead committed Oct 30, 2008
Commits on Sep 11, 2008
Commits on Aug 30, 2008
  1. Add release notes for 0.9.1

    floehopper committed Aug 30, 2008
Commits on Aug 14, 2008
  1. Fixed bug #21465 - expects & stubs should support method names as str…

    …ings (as well as symbols) or fail fast. Convert all expectation method names to a symbol in case they were supplied as a string.
    floehopper committed Aug 14, 2008
  2. Removed unused method.

    floehopper committed Aug 14, 2008
  3. By removing Mock#unexpected_method_called we reduce the number of met…

    …hods vulnerable to the problem that surfaced in bug #21563.
    floehopper committed Aug 14, 2008
  4. Simplify logic in Mock#method_missing so that #unexpected_method_call…

    …ed is only called once.
    floehopper committed Aug 14, 2008
  5. Fix bug #21563 - stubbing 'verified?' method is unsafe. Instance meth…

    …od names on the Mock class should be more obscure.
    floehopper committed Aug 14, 2008
Commits on Jul 24, 2008
Commits on Jul 17, 2008
  1. Now that ClassMethod#method is a string in Ruby 1.8 and a symbol in R…

    …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.
    floehopper committed Jul 17, 2008
  2. It will make life easier if ClassMethod#method and #hidden_method are…

    … both symbols in Ruby 1.9, but strings in Ruby 1.8.
    floehopper committed Jul 17, 2008
  3. ClassMethod#method is normally a symbol, so it makes more sense if #h…

    …idden_method is also a symbol rather than a string.
    floehopper committed Jul 17, 2008
  4. There is no point in running (potentially expensive) checks if config…

    …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.
    floehopper committed Jul 17, 2008
Commits on Jul 11, 2008
Commits on Jul 3, 2008
  1. Fix bug #20883 - never should raise when called to prevent follow up …

    …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.
    floehopper committed Jul 3, 2008