duckpond 1.1.3 → 1.1.4

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA1:
-  metadata.gz: ff44bdc5c03c542af79ff6a7a6c525ad67ca2b81
-  data.tar.gz: 8fda27a470b7ef9cd6744fa1a054a2bd96163b85
+  metadata.gz: 6b28a479d7cc232dbbd474d545caece0c5927ff8
+  data.tar.gz: ffd5f52ff703529d2c96ae47c680d85ab0367bde
 SHA512:
-  metadata.gz: 338d11de6f3c7439d27c92937a150dcd6b2fb2346d556f874bad94a9609fd6cca31f2a6e08e6c6a1e39f35f11e3b9f41e8543d2dceb61af2ae66efa1b3621760
-  data.tar.gz: 5d6c89b8cdc59b2569a2816b422e2ea302ea7c2f70c08ae2229d8817081e44afd74938453a40f0cf26616d3d95da8a68b53b1157c03d9219d76f1c676b2916c0
+  metadata.gz: 5ac93596986601000969400607f1cc2b2f57b78c0e539848a3df6f6cd55fbf11d5f170328a5b7daebf6493c37a27fc5b408f3f416d314b7d9e20df16ffa8ef71
+  data.tar.gz: 8af2817b6a54bd9954fc9b93a965b4699166ef898198283117e74b738d4291b873e48d2b84953aa49fe34681fe9a70bbb10eca9dca38e9e4d9e7c671533d2551

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    duckpond (1.1.2)
+    duckpond (1.1.3)
 
 GEM
   remote: https://rubygems.org/

data/README.md

@@ -69,6 +69,24 @@ various other contracts. This ties in with the reccomendation of preferring comp
       include_clauses_from MyOtherContract
     end
 
+Another feature of duckpond is the ability to specify what your expected result from a contract should be. For example,
+the following contract expects a subject to have a method called "even" and for that method, when called, to return a 
+true value:
+
+    class MyEvenContract < DuckPond::Contract
+      has_method :even?, responds_with: true
+    end
+
+If the method needs args, you can specify those too. This next contract will pass the string "Hell" to the #include? method,
+and expect the value to be true. This contract will therefore be satisfied by strings containing the word "Hell" that are 
+five characters long (such as the word "Hello"):
+
+    class MyHellContract < DuckPond::Contract
+      has_method :include?, responds_with: true, given_args: "Hell"
+      has_method :length, responds_with: 5
+    end
+
+Note: The method will only be *called* if you use the :reponds_with option. Otherwise, it just tests for the method's existence.
 
 In the real world, a contract might look like this:
 

data/lib/duckpond/clause/method_clause.rb

@@ -17,7 +17,25 @@ module DuckPond
     # A subject satisfies a method clause if it responds to that method.
     #
     def satisfied_by?(subject)
-      subject.respond_to? method_name
+
+      # Check the method actually exists.
+      return false unless subject.respond_to? method_name
+
+      # If required, check the response from the method was what the user expected.
+      return false unless _responds_with?(subject, method_name, @options[:responds_with], @options[:given_args])
+
+      true
+    end
+
+    private 
+    #
+    # _responds_with?
+    #
+    # if a method response expectation was passed in, this just calls the method (with the arguments
+    # if given) and does an == compare with the subject.
+    #
+    def _responds_with?(subject, method, expected_result, args = [])
+      return expected_result ? subject.send(method_name, *args) == expected_result : true
     end
 
   end

data/lib/duckpond/version.rb

@@ -1,3 +1,3 @@
 module DuckPond
-  VERSION = "1.1.3"
+  VERSION = "1.1.4"
 end

data/spec/contract_spec.rb

@@ -50,6 +50,17 @@ module DuckPond
     end
   end
 
+  #
+  # see spec/classes/specific_length_contract.rb
+  #
+  describe SpecificLenghtContract do
+    it 'checks a methods response is correct' do
+      expect(SpecificLenghtContract.fulfills?("Hello")).to eq true
+      expect(SpecificLenghtContract.fulfills?("Yello")).to eq false
+      expect(SpecificLenghtContract.fulfills?("Goodbye")).to eq false
+    end
+  end
+
   #
   # See spec/classes/composite_contract.rb
   #

data/spec/spec_helper.rb

@@ -1,5 +1,6 @@
 require 'duckpond'
 require 'classes/contracts/length_contract'
+require 'classes/contracts/specific_length_contract'
 require 'classes/contracts/composite_contract'
 require 'coveralls'
 

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: duckpond
 version: !ruby/object:Gem::Version
-  version: 1.1.3
+  version: 1.1.4
 platform: ruby
 authors:
 - Mikey Hogarth
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2014-06-24 00:00:00.000000000 Z
+date: 2014-06-26 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -88,7 +88,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
 requirements: []
 rubyforge_project: 
-rubygems_version: 2.2.2
+rubygems_version: 2.1.10
 signing_key: 
 specification_version: 4
 summary: Explicit duck-typing for ruby
@@ -99,3 +99,4 @@ test_files:
 - spec/contract_spec.rb
 - spec/inspection_spec.rb
 - spec/spec_helper.rb
+has_rdoc: