pact 1.0.25 → 1.0.26

data/CHANGELOG.md

@@ -2,6 +2,12 @@ Do this to generate your change history
 
     git log --date=relative --pretty=format:'  * %h - %s (%an, %ad)'
 
+### 1.0.26 (5 December 2013)
+
+* e4be654 - BEST COMMIT TO PACT EVER since the introduction of pact:verify. Got rid of the horrific backtraces. (Beth, 5 hours ago)
+* 2810db7 - Updated README to point to realestate-com-au travis CI build (Ronald Holshausen, 28 hours ago)
+* bfa357a - Update README.md (bethesque, 30 hours ago)
+
 ### 1.0.25 (4 December 2013)
 
 * 20dd5fa - Updated the homepage in gemspec (Beth, 4 minutes ago)

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    pact (1.0.25)
+    pact (1.0.26)
       awesome_print (~> 1.1)
       find_a_port (~> 1.0.1)
       json

data/README.md

@@ -8,10 +8,10 @@ This allows testing of both sides of an integration point using fast unit tests.
 
 This gem is inspired by the concept of "Consumer driven contracts". See http://martinfowler.com/articles/consumerDrivenContracts.html for more information.
 
-Travis CI Status: [![travis-ci.org Build Status](https://travis-ci.org/uglyog/pact.png)](https://travis-ci.org/uglyog/pact)
+Travis CI Status: [![travis-ci.org Build Status](https://travis-ci.org/realestate-com-au/pact.png)](https://travis-ci.org/realestate-com-au/pact)
 
 ## Features
-* A services is mocked using an actual process running on a specified port, so javascript clients can be tested as easily as backend clients.
+* A service is mocked using an actual process running on a specified port, so javascript clients can be tested as easily as backend clients.
 * "Provider states" (similar to fixtures) allow the same request to be made with a different expected response.
 * Consumers specify only the fields they are interested in, allowing a provider to return more fields without breaking the pact. This allows a provider to have a different pact with a different consumer, and know which fields each cares about in a given response.
 * Expected interactions are verified to have actually occurred in the consumer specs.
@@ -142,6 +142,7 @@ end
 #### 7. Run the specs again.
 
 Green! You now have a pact file that can be used to verify your expectations in the provider project.
+Now, rinse and repeat for ALL the likely status codes that may be returned (recommend 400, 404, 500 and 401/403 if there is authorisation.)
 
 ### Service Provider project
 

data/lib/pact/provider/pact_spec_runner.rb

@@ -72,6 +72,7 @@ module Pact
         config.extend Pact::Provider::RSpec::ClassMethods
         config.include Pact::Provider::RSpec::InstanceMethods
         config.include Pact::Provider::TestMethods
+        config.backtrace_inclusion_patterns = [/pact\/provider\/rspec/]
 
         config.before :each, :pact => :verify do | example |
           example_description = "#{example.example.example_group.description} #{example.example.description}"

data/lib/pact/version.rb

@@ -1,3 +1,3 @@
 module Pact
-  VERSION = "1.0.25"
+  VERSION = "1.0.26"
 end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: pact
 version: !ruby/object:Gem::Version
-  version: 1.0.25
+  version: 1.0.26
   prerelease: 
 platform: ruby
 authors:
@@ -13,7 +13,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-12-03 00:00:00.000000000 Z
+date: 2013-12-05 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: randexp
@@ -425,7 +425,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
       version: '0'
       segments:
       - 0
-      hash: 963043566746073007
+      hash: 4529256529272671806
 required_rubygems_version: !ruby/object:Gem::Requirement
   none: false
   requirements:
@@ -434,7 +434,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
       segments:
       - 0
-      hash: 963043566746073007
+      hash: 4529256529272671806
 requirements: []
 rubyforge_project: 
 rubygems_version: 1.8.23