Path to this page:
Subject: CVS commit: pkgsrc/devel/ruby-mocha
From: Takahiro Kambe
Date: 2010-12-04 05:01:54
Message id: 20101204040154.65D5E175DD@cvs.netbsd.org
Log Message:
Update ruby-mocha package to 0.9.10.
= 0.9.10 ()
* Added Mocha::ObjectMethods#unstub method - \
https://github.com/floehopper/mocha/issues#issue/6
* Inherit Mocha::ExpectationError from Exception instead of StandardError to \
reduce the chances of a test passing by accident - thanks to James Sanders \
(jsanders) - https://github.com/floehopper/mocha/issues#issue/15
* Fixed bug - GitHub README page to link correctly to code examples - \
https://github.com/floehopper/mocha/issues/closed#issue/11
* Fixed bug - PASSTHROUGH_EXCEPTIONS are defined on MiniTest::Unit::TestCase not \
in Mocha - thanks to Brian Troutwine (blt) - \
https://github.com/floehopper/mocha/issues/closed#issue/14
= 0.9.9 (ee3a79db4d52c3339e8acf07505e01236a2b4810)
* Avoid loading 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, 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
* 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_OPTIONS \
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.
* Explicitly require rubygems for running tests via rake using test-unit gem.
* Handle newer versions of test-unit gem (v2.0.2 to v2.0.9)
* Handle newer versions of minitest gem (v1.4.0 to v1.6.0)
* Added warnings about monkey-patching test-unit and minitest to aid
debugging. These are enabled by including "debug" in the MOCHA_OPTIONS
environment variable. This is now a comma-separated list, so that we can
specify multiple options e.g. MOCHA_OPTIONS=debug,use_test_unit_gem
* Eloy Duran (alloy) made the unit tests run on 1.9.2dev r25249.
* Eloy Duran (alloy) also improved some MiniTest TestResult code I'd written
and got the acceptance tests running on Ruby 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
run with MiniTest. These issues still need investigation.
* Fixed some acceptance tests to run in Ruby 1.9.2 - it's no longer possible
to subvert the protection of a method by calling it via Object#send.
* Fixed "test:performance" rake task so it runs in Ruby 1.9.2.
* 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.
* Luke Redpath (lukeredpath) added new shorthand "any" and \
"all" composite
parameter matchers using "&" and "|". This provides an \
alternative syntax
for expecting any or all matchers to pass,
e.g. foo.expects(:bar).with(equals(1) | equals(2)).
* Improved documentation for Expectation#raises. A number of people have
suggested an extension to the API to cope with custom exceptions that have
extra constructor parameters. However, since the arguments supplied to
Expectation#raises are just passed 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.
* Corrected RDoc example for Expectation#never thanks to Red David (reddavis).
* Improved RDoc including a change suggested by Rohit Arondekar (rohit).
* Updated gemspec as requested by Sam Woodard (shwoodard).
Files: