… commit. Also tidied things up a bit e.g. it's enough to document and test 3 invocations, 2 invocations & 1 invocation - no need for 0 invocations.
…ually. Need to find an automated solution.
…st and Test::Unit::TestCase ends up inheriting from MiniTest::Unit::TestCase. So we need to avoid including the Mocha modules more than once to avoid nasty consequences.
…ed the sshpublisher require into the only rake task that needs it, so that I can at least run the tests in Ruby 1.9. It looks like I will need to build a rake/contrib gem or similar to get this working properly - http://intertwingly.net/blog/2008/01/07/Rake-Contrib-for-1-9
…plugin (now from GitHub instead of RubyForge). Supplied a better link for downloading Mocha files from RubyForge.
…hange from commit cd78ad6.
… so that a floehopper-mocha gem will get built on GitHub.
… cause gem to be auto-built on github
…sed to be used to simulate what ActiveRecord when it messed with Test::Unit, so I could make sure Mocha worked with Rails.
…ubs(with_hash) not working with existing object" , following the principle of least surprise, it should be possible to call ObjectMethods#expects & ObjectMethods#stubs with a Hash of method_names vs return_values like you can with Mock#expects & Mock#stubs. I've extracted out some shared logic into the ArgumentIterator - not sure this is the best solution, but at least it keeps duplication to a minimum. I've also updated & improved the docs to reflect the changes.  http://rubyforge.org/tracker/index.php?func=detail&aid=23055&group_id=1917&atid=7480
… talk at Ruby Manor, any methods added to core classes are now added by including a module. This means that Mocha is a better citizen of the Ruby world and it's behaviour is more easily extended.  http://blog.jayfields.com/2008/07/ruby-underuse-of-modules.html & http://blog.jayfields.com/2008/07/ruby-redefine-method-behavior.html