Revisions of rubygem-rspec-mocks
buildservice-autocommit
accepted
request 287848
from
Stephan Kulow (coolo)
(revision 24)
baserev update by copy to link target
- updated to version 3.2.1 Bug Fixes: * Add missing `rspec/support/differ` require so that rspec-mocks can be used w/o rspec-expectations (which also loads the differ and hided the fact we forgot to require it). (Myron Marston, #893) * Revert tracking of received arg mutation (added in 3.2.0 to provide an error in a situation we can't support) as our implementation has side effects on non-standard objects and there's no solution we could come up with that always works. (Myron Marston, #900)
buildservice-autocommit
accepted
request 284561
from
Stephan Kulow (coolo)
(revision 22)
baserev update by copy to link target
- update to 3.1.3: * Rails 4.1 [too many changes to list here, see http://www.rubydoc.info/gems/rspec-mocks/file/Changelog.md ]
buildservice-autocommit
accepted
request 256108
from
Stephan Kulow (coolo)
(revision 19)
baserev update by copy to link target
adapt to new rubygem packaging
buildservice-autocommit
accepted
request 223801
from
Factory Maintainer (factory-maintainer)
(revision 17)
baserev update by copy to link target
buildservice-autocommit
accepted
request 221436
from
Factory Maintainer (factory-maintainer)
(revision 15)
baserev update by copy to link target
buildservice-autocommit
accepted
request 204167
from
Stephan Kulow (coolo)
(revision 13)
baserev update by copy to link target
initialized devel package after accepting 201913
- updated to version 2.14.2 Bug Fixes: * Fix `as_null_object` doubles so that they return `nil` from `to_ary` (Jon Rowe). * Fix regression in 2.14 that made `stub!` (with an implicit receiver) return a test double rather than stub a method (Myron Marston). ### 2.14.1 / 2013-07-07 [full changelog](http://github.com/rspec/rspec-mocks/compare/v2.14.0...v2.14.1) Bug Fixes: * Restore `double.as_null_object` behavior from 2.13 and earlier: a double's nullness persisted between examples in earlier examples. While this is not an intended use case (test doubles are meant to live for only one example), we don't want to break behavior users rely on in a minor relase. This will be deprecated in 2.99 and removed in 3.0. (Myron Marston) ### 2.14.0 / 2013-07-06 [full changelog](http://github.com/rspec/rspec-mocks/compare/v2.14.0.rc1...v2.14.0) Enhancements: * Document test spies in the readme. (Adarsh Pandit) * Add an `array_including` matcher. (Sam Phippen) * Add a syntax-agnostic API for mocking or stubbing a method. This is intended for use by libraries such as rspec-rails that need to mock or stub a method, and work regardless of the syntax the user has
- updated to version 2.13.1 Bug fixes * Allow a block implementation to be used in combination with `and_yield`, `and_raise`, `and_return` or `and_throw` (Myron Marston).
- updated to version 2.12.2 [full changelog](http://github.com/rspec/rspec-mocks/compare/v2.12.1...v.2.12.2) Bug fixes * Fix `and_call_original` to work properly for methods defined on a module extended onto an object instance (Myron Marston). * Fix `stub_const` with an undefined constnat name to work properly with constant strings that are prefixed with `::` -- and edge case I missed in the bug fix in the 2.12.1 release (Myron Marston). * Ensure method visibility on a partial mock is restored after reseting method stubs, even on a singleton module (created via `extend self`) when the method visibility differs between the instance and singleton versions (Andy Lindeman).
Displaying revisions 41 - 60 of 65