lazy_mock 1.0

data/MIT-LICENSE

@@ -0,0 +1,20 @@
+Copyright (c) 2011 Sage http://sage.com/
+
+Permission is hereby granted, free of charge, to any person obtaining
+a copy of this software and associated documentation files (the
+"Software"), to deal in the Software without restriction, including
+without limitation the rights to use, copy, modify, merge, publish,
+distribute, sublicense, and/or sell copies of the Software, and to
+permit persons to whom the Software is furnished to do so, subject to
+the following conditions:
+
+The above copyright notice and this permission notice shall be
+included in all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE
+LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION
+OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION
+WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

data/README.rdoc

@@ -0,0 +1,39 @@
+= LazyMocks
+
+== Rationale
+
+In Rspec, using a mock object, the moer functionality you add, the more complaints you get about unexpected messages.
+
+Sometimes you just want an object that responds to anything you throw at it, and just stub specifc behavior.
+
+Enter LazyMocks.
+
+== Usage
+
+Every method returns a new instance of LazyMock.
+
+    my_mock = LazyMock.new
+    my_mock.some_method_that_doesnt_exist
+    => #<MyMock>
+
+It responds to everything.
+
+    my_mock = LazyMock.new
+    my_mock.respond_to?(:huh?)
+    => true
+
+Then you can stub what you want to.
+
+    my_mock = LazyMock.new
+    my_mock.stub(:something).and_return('foo')
+
+Because it returns an instance of iteself, any code paths (the first traversed) will pass:
+
+    my_mock = LazyMock.new
+    if my_mock.thing.other_method.another_method
+      return "Test"  if my_mock.has_some_method?
+    else
+      #not getting here..
+    end
+
+This means that for paths in your specs which you don't care about (because you're testing one specific part) won't break when you add new functionality as you flesh out your implementation.

data/lib/lazy_mock.rb

@@ -0,0 +1,5 @@
+class LazyMock < BasicObject
+  def method_missing(*args)
+    ::LazyMock.new
+  end
+end

metadata

@@ -0,0 +1,60 @@
+--- !ruby/object:Gem::Specification
+name: lazy_mock
+version: !ruby/object:Gem::Version
+  version: '1.0'
+  prerelease: 
+platform: ruby
+authors:
+- SageOne
+autorequire: 
+bindir: bin
+cert_chain: []
+date: 2011-08-26 00:00:00.000000000 +01:00
+default_executable: 
+dependencies:
+- !ruby/object:Gem::Dependency
+  name: rspec
+  requirement: &80080220 !ruby/object:Gem::Requirement
+    none: false
+    requirements:
+    - - ! '>='
+      - !ruby/object:Gem::Version
+        version: '0'
+  type: :development
+  prerelease: false
+  version_requirements: *80080220
+description: Lazy Mocks just respond to anything you throw at them.
+email: sageone@sage.com
+executables: []
+extensions: []
+extra_rdoc_files: []
+files:
+- lib/lazy_mock.rb
+- README.rdoc
+- MIT-LICENSE
+has_rdoc: true
+homepage: http://github.com/Sage/lazy_mocks
+licenses: []
+post_install_message: 
+rdoc_options: []
+require_paths:
+- lib
+required_ruby_version: !ruby/object:Gem::Requirement
+  none: false
+  requirements:
+  - - ! '>='
+    - !ruby/object:Gem::Version
+      version: 1.9.2
+required_rubygems_version: !ruby/object:Gem::Requirement
+  none: false
+  requirements:
+  - - ! '>='
+    - !ruby/object:Gem::Version
+      version: 1.3.6
+requirements: []
+rubyforge_project: 
+rubygems_version: 1.6.2
+signing_key: 
+specification_version: 3
+summary: Lazy Mocks - They respond to everything man!!
+test_files: []