gimme 0.1.8 → 0.2.0

data/Gemfile

@@ -4,6 +4,8 @@ source "http://rubygems.org"
 # Add dependencies to develop your gem here.
 # Include everything needed to run rake, tests, features, etc.
 group :development, :test do
+  gem 'pry'
+
   gem 'rdoc'
 
   gem "jeweler", "~> 1.5.2"
@@ -14,7 +16,7 @@ group :development, :test do
   gem "guard-cucumber", :require => false
   gem "simplecov", :require => false
   if RUBY_PLATFORM =~ /darwin/i
-    gem "growl_notify"
+    gem "growl"
     gem "rb-fsevent", :require => false
   end
 end

data/Gemfile.lock

@@ -2,6 +2,7 @@ GEM
   remote: http://rubygems.org/
   specs:
     builder (3.0.0)
+    coderay (1.0.5)
     cucumber (1.1.9)
       builder (>= 2.1.2)
       diff-lcs (>= 1.1.2)
@@ -13,8 +14,7 @@ GEM
     gherkin (2.9.0)
       json (>= 1.4.6)
     git (1.2.5)
-    growl_notify (0.0.3)
-      rb-appscript
+    growl (1.0.3)
     guard (1.0.0)
       ffi (>= 0.5.0)
       thor (~> 0.14.6)
@@ -28,9 +28,13 @@ GEM
       git (>= 1.2.5)
       rake
     json (1.6.5)
+    method_source (0.7.0)
     multi_json (1.1.0)
+    pry (0.9.8)
+      coderay (~> 1.0.5)
+      method_source (~> 0.7)
+      slop (>= 2.4.3, < 3)
     rake (0.9.2.2)
-    rb-appscript (0.6.1)
     rb-fsevent (0.9.0)
     rdoc (3.12)
       json (~> 1.4)
@@ -48,6 +52,7 @@ GEM
       multi_json (~> 1.0)
       simplecov-html (~> 0.5.3)
     simplecov-html (0.5.3)
+    slop (2.4.3)
     term-ansicolor (1.0.7)
     thor (0.14.6)
 
@@ -56,10 +61,11 @@ PLATFORMS
 
 DEPENDENCIES
   cucumber
-  growl_notify
+  growl
   guard-cucumber
   guard-rspec
   jeweler (~> 1.5.2)
+  pry
   rb-fsevent
   rdoc
   rspec

data/README.markdown

@@ -8,7 +8,7 @@ And here's a [blog post outlining the case for gimme](http://searls.test-double.
 
 ## Basics (or "What does it Gimme?" ... har.)
 
-Gimme was originally named (well, for the first five hours of its life) "[Tabula Rasa](http://en.wikipedia.org/wiki/Tabula_rasa)," to very clearly indicate that it generates blank slate test doubles that lack any initial coupling with the concepts associated with specific [test double](http://xunitpatterns.com/Test%20Double.html) subtypes like mocks/stubs/fakes/spies/proxies. But in the end, "gimme" was easier to type than "tabula rasa", and I generally wanted to avoid test pattern lingo from leaking into the context and language of everybody's tests (hence no method named "stub"). 
+Gimme was originally named (well, for the first five hours of its life) "[Tabula Rasa](http://en.wikipedia.org/wiki/Tabula_rasa)," to very clearly indicate that it generates blank slate test doubles that lack any initial coupling with the concepts associated with specific [test double](http://xunitpatterns.com/Test%20Double.html) subtypes like mocks/stubs/fakes/spies/proxies. But in the end, "gimme" was easier to type than "tabula rasa", and I generally wanted to avoid test pattern lingo from leaking into the context and language of everybody's tests (hence no method named "stub").
 
 Gimme doubles are most accurately identified as [test spies](http://xunitpatterns.com/Test%20Spy.html) in [this table discriminating the types](http://xunitpatterns.com/Mocks,%20Fakes,%20Stubs%20and%20Dummies.html) over at Gerard Meszaros' helpful xUnit patterns repository.
 
@@ -44,35 +44,35 @@ Once you're in your test or spec, to create a test double.
 If you know what what class your SUT will be depending on, you can specify it:
 
     double = gimme(Object)
-    
+
 Or you could just create a generic double can stub/verify any method you need:
 
     double = gimme()
-     
-### Stubbing     
-     
+
+### Stubbing
+
 Once you have your double, you can stub methods:
 
     give(double).to_s { 'Pants' }
     double.to_s                         #=> 'Pants'
-    
+
     give(double).equal?(:ninja) { true }
-    give(double).equal?(:fruit) { false }    
+    give(double).equal?(:fruit) { false }
     double.equal?(:ninja)               #=> true
-    
+
 You can also stub your double to raise an exception (or really, do anything in the passed block):
 
     dog = gimme(Dog)
     give(dog).holler_at(:mail_man) { raise LeashLawError }
-    
+
     dog.holler_at(:mail_man) # raises LeashLawError
 
-### Verifying    
-    
-You can also verify interactions with your double    
+### Verifying
+
+You can also verify interactions with your double
 
     double.equal?(:fruit)
-    
+
     verify(double).equal?(:fruit)       # passes verification (read: does nothing)
     verify(double).equal?(:what_the)    # fails verification (raises a Gimme::VerifyFailedError)
 
@@ -80,9 +80,9 @@ You can also specify how many times a specific invocation should have occurred (
 
     double.equal?(:fruit)
     double.equal?(:fruit)
-    
+
     verify(double,2).equal?(:fruit)
-    
+
 ### Using Argument Matchers
 
 Gimme includes several argument matchers which can be used to control which invocations will satisfy a particular stubbing or verification.
@@ -92,24 +92,24 @@ Gimme includes several argument matchers which can be used to control which invo
 Replacing an argument with `anything` will instantiate a `Gimme::Matchers::Anything` matcher, which always returns true, regardless of what gets passed in.
 
     give(dog).walk_to(anything,5) { 'Park' }
-    
+
     walk_to(3,5)          #=> 'Park'
     walk_to('pants',5)    #=> 'Park'
-    walk_to(nil,5)        #=> 'Park'        
+    walk_to(nil,5)        #=> 'Park'
     walk_to(3,5.1)        #=> nil
-        
+
 Matchers can be used when both stubbing and verifying a method. To verify on anything, you could:
 
     dog.holler_at(true)
-    
-    verify(dog).holler_at(anything) #=> passes verification    
-    
-Other matchers:    
-    
+
+    verify(dog).holler_at(anything) #=> passes verification
+
+Other matchers:
+
 * **is_a(class)** — matches any arguments that are `kind_of?` the provided class
 * **any(class)** — same as `is_a`, but also matches nil
 * **boolean** — matches true or false arguments
-* **numeric** — matches numeric arguments 
+* **numeric** — matches numeric arguments
 
 See the [cucumber feature for examples using these matchers](http://relishapp.com/searls/gimme/stubbing-with-matchers)
 
@@ -125,7 +125,7 @@ that can respond to `matches?(arg)`. Maybe something like this would work (even
     end
 
     give(dog).introduce_to(Nothing.new) { :meow }     #b/c Nothing.matches? always returns false, :meow will never returned by the double.
-    
+
 
 ### Using Argument Captors
 
@@ -140,23 +140,23 @@ In cases like these, a captor can be used to "capture" the real argument value t
 
     #act
     sut.submit_query_for_string("find dogs")
-    
+
     #assert
     verify(searches_system).execute(capture(query_captor))
     query_captor.value.table_name.should == "Dogs"
 
-    
+
 ### Suppressing NoMethodError
 
 You may be reading this section because you got this message:
 
-    The Test Double of <Class Name> may not know how to respond to the '<Method Name>' method. 
+    The Test Double of <Class Name> may not know how to respond to the '<Method Name>' method.
       If you're confident that a real Kernel will know how to respond to '<Method Name>', then you can
       invoke give! or verify! to suppress this error.
-    
+
 Whenever you stub or verify a method against a test double on a class, gimme will first verify that the method can be found on the class being
 doubled. Since the vast majority of methods can be verified in this way, this default behavior is designed to provide fast failure.
-This can be really handy, whether the cause is as simple as a transcription error of a method name from irb or as convoluted as an incorrect version of a dependency that lacks the method you expected. 
+This can be really handy, whether the cause is as simple as a transcription error of a method name from irb or as convoluted as an incorrect version of a dependency that lacks the method you expected.
 
 However, because classes can be reopened and edited at runtime, often you'll outsmart gimme by knowing that a particular
 method *will* be available on the class being doubled, even though it isn't *right now*.
@@ -167,15 +167,15 @@ Here's an example where our Dog is again being doubled to facilitate some test,
 
     dog = gimme(Dog)
     give!(dog).meow { :purr }
-    
+
     dog.meow              #=> :purr
-    
+
 We cam accomplish the same thing using `verify!`:
 
     dog = gimme(Dog)
-    
+
     dog.meow
-    
+
     verify!(dog).meow     #=> verification passes, even though gimme can't see the meow method.
 
 ### gimme_next
@@ -185,7 +185,7 @@ To my knowledge, there isn't an established pattern or name for this next featur
 Take this example method from the RSpec book:
 
     def guess(guess)
-      marker = Marker.new(@secret,guess)  
+      marker = Marker.new(@secret,guess)
       @output.puts '+'*marker.exact_match_count + '-'*marker.number_match_count
     end
 
@@ -195,21 +195,21 @@ This can be tested with gimme in isolation (meaning that a real Marker object is
       let(:marker) { gimme_next(Marker) }
       before do
         give(marker).exact_match_count { 4 }
-        give(marker).number_match_count { 0 }                 
+        give(marker).number_match_count { 0 }
 
         game.guess('1234')
       end
-      
+
       it 'instantiates a marker with the secret and guess' do
         verify!(marker).initialize('1234','1234')
       end
-      
+
       it 'outputs the exact matches followed by the number matches' do
         verify(output).puts('++++')
-      end      
+      end
     end
 
-As you can see above, `gimme_next(Marker)` will create a double just like `gimme()` would have, but it will also temporarily redefine the passed class's `new` method such that the next instantiation of that class (presumably by the SUT) will return the same double.* 
+As you can see above, `gimme_next(Marker)` will create a double just like `gimme()` would have, but it will also temporarily redefine the passed class's `new` method such that the next instantiation of that class (presumably by the SUT) will return the same double.*
 
 This way we can clearly specify the SUT's interaction with the Marker class while maintaining its isolation.
 
@@ -218,4 +218,4 @@ This way we can clearly specify the SUT's interaction with the Marker class whil
 ## About
 
 ### Maintainers
-* [Justin Searls](http://about.emw/searls), [Pillar Technology](http://pillartechnology.com)
+* [Justin Searls](http://about.emw/searls), [test double](http://test-double.com)

data/Rakefile

@@ -43,6 +43,11 @@ Cucumber::Rake::Task.new do |t|
   t.cucumber_opts = %w{--format progress}
 end
 
+Cucumber::Rake::Task.new('cucumber:wip') do |t|
+  t.cucumber_opts = %w{--format progress --wip --tags @wip}
+end
+
+
 require 'rspec/core/rake_task'
 RSpec::Core::RakeTask.new
 

data/VERSION

@@ -1 +1 @@
-0.1.8
+0.2.0

data/features/step_definitions/gimme_steps.rb

@@ -26,7 +26,21 @@ When /^I stub #{METHOD_PATTERN} to raise (.*)$/ do |method,args,error_type|
   sendish(give(@double),method,args,"raise #{error_type}")
 end
 
-# Invoking
+## class stubbing
+Given /^the (.*) class$/ do |cls|
+  @double = eval(cls)
+end
+
+When /^I reset Gimme$/ do
+  Gimme.reset
+end
+
+Then /^#{METHOD_PATTERN} no longer returns (.*)$/ do |method,args,result|
+  sendish(@double,method,args).should_not == eval(result)
+end
+
+
+# stubbing invocation
 
 Then /^invoking #{METHOD_PATTERN} returns (.*)$/ do |method,args,result|
   sendish(@double,method,args).should == eval(result)

data/features/stub_class_methods.feature

@@ -0,0 +1,21 @@
+@wip
+Feature: stubbing class methods
+
+  In order to spec code that depends on Rails or other APIs that make
+    liberal use of class methods, I want to stub class methods
+    and see that the classes are restored after each spec run.
+
+
+  Scenario Outline: stubbing class method
+    Given the Possum class
+    When I stub <method> to return <gives>
+    Then invoking <invocation> returns <returns>
+
+    When I reset Gimme
+    Then <method> no longer returns <gives>
+
+  Scenarios: the anything matcher with a one-argument method
+    | method             | gives | invocation        | returns |
+    | crawl_to(anything) | '…'   | crawl_to(Cat.new) | '…'     |
+    | crawl_to(anything) | '…'   | crawl_to(Dog.new) | '…'     |
+    | crawl_to(anything) | '…'   | crawl_to(nil)     | '…'     |

data/features/support/animals.rb

@@ -10,12 +10,20 @@ end
 class Animal
 end
 
+class Possum
+  def self.sleep
+  end
+
+  def self.crawl_to(location)
+  end
+end
+
 class Dog < Animal
   include Eater
-    
+
   # to exercise stub & verify of attributes: matching(regex)
   attr_accessor :name
-  
+
   def walk_to(x,y)
     'use me to exercise numeric matchers: numeric, less_than, greater_than, within_range'
   end
@@ -23,23 +31,23 @@ class Dog < Animal
   def introduce_to(animal)
     'use me to exercise identity matchers: anything, is_a(Animal), is_a(Cat), any(Animal), any(Dog)'
   end
-  
+
   def holler_at(loudly)
     'use me to exercise: boolean'
   end
-  
+
   def use_toys(hash_of_toys_and_actions)
     'use me to exercise: hash_including'
   end
-  
+
   def clean_toys(array_of_toys)
     'use me to exercise: including'
   end
-  
+
   def purebred?
     'stub me to return a boolean'
   end
-  
+
 end
 
 class Cat < Animal
@@ -49,7 +57,7 @@ class Turtle < Animal
   def initialize(shell)
     @shell = shell
   end
-  
+
   def swim
   end
 end

data/gimme.gemspec

@@ -5,11 +5,11 @@
 
 Gem::Specification.new do |s|
   s.name = %q{gimme}
-  s.version = "0.1.8"
+  s.version = "0.2.0"
 
   s.required_rubygems_version = Gem::Requirement.new(">= 0") if s.respond_to? :required_rubygems_version=
   s.authors = [%q{Justin Searls}]
-  s.date = %q{2012-02-25}
+  s.date = %q{2012-02-27}
   s.description = %q{gimme attempts to bring to Ruby a test double workflow akin to Mockito in Java. Major distinctions include preserving arrange-act-assert in tests, fast feedback for methods the double's real counterpart may not know how to respond to, no string/symbolic representations of methods, argument captors, and strong opinions (weakly held). }
   s.email = %q{searls@gmail.com}
   s.extra_rdoc_files = [
@@ -32,6 +32,7 @@ Gem::Specification.new do |s|
     "features/gimme_next.feature",
     "features/step_definitions/gimme_steps.rb",
     "features/stub_basic.feature",
+    "features/stub_class_methods.feature",
     "features/stub_matchers.feature",
     "features/stub_sensible_defaults.feature",
     "features/support/animals.rb",
@@ -44,17 +45,25 @@ Gem::Specification.new do |s|
     "lib/gimme-double.rb",
     "lib/gimme.rb",
     "lib/gimme/captor.rb",
+    "lib/gimme/dsl.rb",
     "lib/gimme/errors.rb",
     "lib/gimme/gives.rb",
+    "lib/gimme/gives_class_methods.rb",
+    "lib/gimme/invokes_satisfied_stubbing.rb",
     "lib/gimme/matchers.rb",
-    "lib/gimme/method_resolver.rb",
+    "lib/gimme/reset.rb",
+    "lib/gimme/resolves_methods.rb",
     "lib/gimme/rspec_adapter.rb",
     "lib/gimme/test_double.rb",
     "lib/gimme/verifies.rb",
     "spec/gimme/captor_spec.rb",
     "spec/gimme/errors_spec.rb",
+    "spec/gimme/gives_class_methods_spec.rb",
     "spec/gimme/gives_spec.rb",
     "spec/gimme/matchers_spec.rb",
+    "spec/gimme/resolves_methods_spec.rb",
+    "spec/gimme/rspec_adapter_spec.rb",
+    "spec/gimme/shared_examples/shared_gives_examples.rb",
     "spec/gimme/test_double_spec.rb",
     "spec/gimme/verifies_spec.rb",
     "spec/spec_helper.rb"
@@ -67,8 +76,12 @@ Gem::Specification.new do |s|
   s.test_files = [
     "spec/gimme/captor_spec.rb",
     "spec/gimme/errors_spec.rb",
+    "spec/gimme/gives_class_methods_spec.rb",
     "spec/gimme/gives_spec.rb",
     "spec/gimme/matchers_spec.rb",
+    "spec/gimme/resolves_methods_spec.rb",
+    "spec/gimme/rspec_adapter_spec.rb",
+    "spec/gimme/shared_examples/shared_gives_examples.rb",
     "spec/gimme/test_double_spec.rb",
     "spec/gimme/verifies_spec.rb",
     "spec/spec_helper.rb"
@@ -78,6 +91,7 @@ Gem::Specification.new do |s|
     s.specification_version = 3
 
     if Gem::Version.new(Gem::VERSION) >= Gem::Version.new('1.2.0') then
+      s.add_development_dependency(%q<pry>, [">= 0"])
       s.add_development_dependency(%q<rdoc>, [">= 0"])
       s.add_development_dependency(%q<jeweler>, ["~> 1.5.2"])
       s.add_development_dependency(%q<rspec>, [">= 0"])
@@ -86,11 +100,12 @@ Gem::Specification.new do |s|
       s.add_development_dependency(%q<cucumber>, [">= 0"])
       s.add_development_dependency(%q<guard-cucumber>, [">= 0"])
       s.add_development_dependency(%q<simplecov>, [">= 0"])
-      s.add_development_dependency(%q<growl_notify>, [">= 0"])
+      s.add_development_dependency(%q<growl>, [">= 0"])
       s.add_development_dependency(%q<rb-fsevent>, [">= 0"])
       s.add_development_dependency(%q<rspec>, [">= 1.3.1"])
       s.add_development_dependency(%q<cucumber>, [">= 0.10.0"])
     else
+      s.add_dependency(%q<pry>, [">= 0"])
       s.add_dependency(%q<rdoc>, [">= 0"])
       s.add_dependency(%q<jeweler>, ["~> 1.5.2"])
       s.add_dependency(%q<rspec>, [">= 0"])
@@ -99,12 +114,13 @@ Gem::Specification.new do |s|
       s.add_dependency(%q<cucumber>, [">= 0"])
       s.add_dependency(%q<guard-cucumber>, [">= 0"])
       s.add_dependency(%q<simplecov>, [">= 0"])
-      s.add_dependency(%q<growl_notify>, [">= 0"])
+      s.add_dependency(%q<growl>, [">= 0"])
       s.add_dependency(%q<rb-fsevent>, [">= 0"])
       s.add_dependency(%q<rspec>, [">= 1.3.1"])
       s.add_dependency(%q<cucumber>, [">= 0.10.0"])
     end
   else
+    s.add_dependency(%q<pry>, [">= 0"])
     s.add_dependency(%q<rdoc>, [">= 0"])
     s.add_dependency(%q<jeweler>, ["~> 1.5.2"])
     s.add_dependency(%q<rspec>, [">= 0"])
@@ -113,7 +129,7 @@ Gem::Specification.new do |s|
     s.add_dependency(%q<cucumber>, [">= 0"])
     s.add_dependency(%q<guard-cucumber>, [">= 0"])
     s.add_dependency(%q<simplecov>, [">= 0"])
-    s.add_dependency(%q<growl_notify>, [">= 0"])
+    s.add_dependency(%q<growl>, [">= 0"])
     s.add_dependency(%q<rb-fsevent>, [">= 0"])
     s.add_dependency(%q<rspec>, [">= 1.3.1"])
     s.add_dependency(%q<cucumber>, [">= 0.10.0"])