pact 1.0.20 → 1.0.21

data/.travis.yml

@@ -0,0 +1,8 @@
+language: ruby
+rvm:
+  - 1.9.3
+  - 2.0.0
+  - jruby-19mode
+  - jruby-20mode
+  - ruby-head
+  - jruby-head

data/CHANGELOG.md

@@ -2,6 +2,28 @@ Do this to generate your change history
 
     git log --date=relative --pretty=format:'  * %h - %s (%an, %ad)'
 
+### 1.0.21 (25 November 2013)
+
+* f810795 - add jruby 2.0 to travis (Ronald Holshausen, 4 days ago)
+* 65e0ea2 - dropped rbx as it was failing in a crazy way (Ronald Holshausen, 4 days ago)
+* 1403594 - added ruby 2 to travis (Ronald Holshausen, 4 days ago)
+* c72662e - rbx requires the rubysl-thwait gem (Ronald Holshausen, 4 days ago)
+* 70745dc - require webrick (Ronald Holshausen, 4 days ago)
+* 43110ad - removed thin as a runtime dependancy as it is not supported on all rubies (Ronald Holshausen, 4 days ago)
+* d4eea58 - dropped all rubies < 1.9.3 (Ronald Holshausen, 4 days ago)
+* cb312b5 - removed debugger as a development dependancy as it will not build on all rubies (Ronald Holshausen, 4 days ago)
+* 872c649 - removed ruby 1.9.2 as active support does not active support it (Ronald Holshausen, 4 days ago)
+* 1930269 - added travis CI for the uglyog repo (Ronald Holshausen, 4 days ago)
+* 7750ee1 - added travis build status image (Ronald Holshausen, 5 days ago)
+* 9f72b31 - added travis build status image (Ronald Holshausen, 5 days ago)
+* d9be65b - Added .travis.yml (Beth, 6 days ago)
+* e7a7e7b - Refactoring pact_helper loading. (Beth, 6 days ago)
+* 0224d36 - Only log loading of pact_helper once https://github.com/uglyog/pact/issues/8 (Beth, 6 days ago)
+* 0123207 - Updating gemspec description (Beth, 7 days ago)
+* 697cbdc - Updating README.md (Beth, 4 weeks ago)
+* ca79968 - Investigating Rack and HTTP headers in response to https://github.com/uglyog/pact/issues/6. Updated tests and README with info on multiple headers with the same name. (B
+* 01f0b9a - Updating README (Beth, 4 weeks ago)
+
 ### 1.0.20 (29 October 2013)
 
   * c03f34f - Fixed the pretty generation of JSON when active support is loaded. It is both a sad and a happy moment. (Beth, 7 minutes ago)

data/Gemfile

@@ -2,3 +2,5 @@ source 'https://rubygems.org'
 
 # Specify your gem's dependencies in pact.gemspec
 gemspec
+
+gem 'geminabox-client'

data/Gemfile.lock

@@ -1,15 +1,15 @@
 PATH
   remote: .
   specs:
-    pact (1.0.20)
+    pact (1.0.21)
       awesome_print (~> 1.1.0)
       find_a_port (~> 1.0.1)
       json
       rack-test (~> 0.6.2)
       randexp (~> 0.1.7)
       rspec (~> 2.12)
-      thin
       thor
+      webrick
 
 GEM
   remote: https://rubygems.org/
@@ -24,18 +24,9 @@ GEM
     atomic (1.1.14)
     awesome_print (1.1.0)
     coderay (1.0.9)
-    columnize (0.3.6)
     crack (0.4.1)
       safe_yaml (~> 0.9.0)
-    daemons (1.1.9)
-    debugger (1.6.2)
-      columnize (>= 0.3.1)
-      debugger-linecache (~> 1.2.0)
-      debugger-ruby_core_source (~> 1.2.3)
-    debugger-linecache (1.2.0)
-    debugger-ruby_core_source (1.2.3)
     diff-lcs (1.2.4)
-    eventmachine (1.0.3)
     fakefs (0.4.2)
     find_a_port (1.0.1)
     geminabox-client (0.0.2)
@@ -68,10 +59,6 @@ GEM
     rspec-mocks (2.14.3)
     safe_yaml (0.9.5)
     slop (3.4.6)
-    thin (1.6.0)
-      daemons (>= 1.0.9)
-      eventmachine (>= 1.0.0)
-      rack (>= 1.5.0)
     thor (0.18.1)
     thread_safe (0.1.3)
       atomic
@@ -79,13 +66,13 @@ GEM
     webmock (1.9.3)
       addressable (>= 2.2.7)
       crack (>= 0.3.2)
+    webrick (1.3.1)
 
 PLATFORMS
   ruby
 
 DEPENDENCIES
   activesupport
-  debugger
   fakefs (~> 0.4)
   geminabox-client
   hashie (~> 2.0)

data/README.md

@@ -9,6 +9,8 @@ This allows you to test 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)
+
 ## 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.
 * "Provider states" (similar to fixtures) allow the same request to be made with a different expected response.
@@ -23,53 +25,49 @@ Put it in your Gemfile. You know how.
 
 ## Usage
 
-### Configuration
+### Service Consumer project
+
+#### 1. Start with you model
+
+Imagine a model class that looks something like this. The attributes for a SomethingModel live on a remote server, and will need to be retrieved by an HTTP call.
 
 ```ruby
-Pact.configure do | config |
-  config.pact_dir = "???" # Optional, default is ./spec/pacts
-  config.log_dir = "???" # Optional, default is ./log
-  config.logger = "??" # Optional, defaults to a file logger to the configured log_dir.
-  config.logger.level = Logger::DEBUG #By default this is INFO, bump this up to debug for more detailed logs
-  config.pactfile_write_mode = :ovewrite / :update / :smart # Optional. The default pactfile_write_mode is :overwrite. See notes in Advanced section for further information.
+class SomethingModel
+  attr_reader :name
+
+  def intialize name
+    @name = name
+  end
+
+  def == other
+    other.is_a?(Something) && other.name == name
+  end
 end
 ```
 
-### Service Consumer project
+#### 2. Create a skeleton client class
 
-#### Create a Consumer Driven Contract (pact file) using the spec for your client class
+Imagine a service provider client class that looks something like this.
 
 ```ruby
 
-# Imagine a service provider client class that looks something like this
-
 class MyServiceProviderClient
   include HTTParty
   base_uri 'http://my-service'
 
   def get_something
-    name = JSON.parse(self.class.get("/something").body)['name']
-    Something.new(name)
+    # Yet to be implemented because we're doing Test First Development...
   end
 end
 
-class Something
-  attr_reader :name
-
-  def intialize name
-    @name = name
-  end
+```
+#### 3. Configure the mock server
 
-  def == other
-    other.is_a?(Something) && other.name == name
-  end
-end
+The following code will create a mock service on localhost:1234 which will respond to your application's queries over HTTP as if it were the real "My Service Provider" app. It also creats a mock service provider object which you will use to set up your expectations. The method name to access the mock service provider will be what ever name you give as the service argument - in this case "my_service_provider"
 
 
-# The following code creates a service on localhost:1234 which will respond to your application's queries
-# over HTTP as if it were the real "My Service Provider" app. It also creats a mock service provider object
-# which you will use to set up your expectations. The method name to access the mock service provider
-# will be what ever name you give as the service argument - in this case "my_service_provider"
+```ruby
+# In /spec/service_providers/pact_helper.rb
 
 require 'pact/consumer/rspec'
 
@@ -80,9 +78,14 @@ Pact.service_consumer "My Service Consumer" do
     end
   end
 end
+```
 
-# Use the :pact => true describe metadata to include all the pact generation functionality in your spec.
+#### 4. Write a failing spec for the client
+
+```ruby
+# In /spec/service_providers/my_service_provider_client_spec.rb
 
+# Use the :pact => true describe metadata to include all the pact generation functionality in your spec.
 describe MyServiceProviderClient, :pact => true do
 
   before do
@@ -104,7 +107,7 @@ describe MyServiceProviderClient, :pact => true do
     end
 
     it "returns a Something" do
-      expect(MyServiceProviderClient.get_something).to eq(Something.new('A small something'))
+      expect(MyServiceProviderClient.get_something).to eq(SomethingModel.new('A small something'))
     end
 
   end
@@ -113,27 +116,45 @@ end
 
 ```
 
+#### 5. Run the specs
+
 Running the consumer spec will generate a pact file in the configured pact dir (spec/pacts by default).
 Logs will be output to the configured log dir that can be useful when diagnosing problems.
 
-To run your consumer app as a process during your test (eg for a Capybara test):
+Of course, the above specs will fail because the client method is not implemented, so next, implement your client methods.
+
+#### 6. Implement the client methods
 
 ```ruby
-Pact.service_consumer "My Consumer" do
-  app my_consumer_rack_app
-  port 4321
+
+class MyServiceProviderClient
+  include HTTParty
+  base_uri 'http://my-service'
+
+  def get_something
+    name = JSON.parse(self.class.get("/something").body)['name']
+    SomethingModel.new(name)
+  end
 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.
+
 ### Service Provider project
 
-#### Configure your service provider
+#### 1. Create the skeleton API classes
+
+Create your API class using the framework of your choice (e.g. Sinatra, Grape) - leave the methods unimplemented, we're doing Test First Develoment, remember?
 
-Create a `pact_helper.rb` in your service provider project. The file must be called pact_helper.rb, however there is some flexibility in where it can be stored. The recommended place is `specs/service_providers/pact_helper.rb`.
+#### 2. Tell your provider that it needs to honour the pact file you made earlier
+
+Create a `pact_helper.rb` in your service provider project. The file must be called pact_helper.rb, however there is some flexibility in where it can be stored. The recommended place is `specs/service_consumers/pact_helper.rb`.
 
 ```ruby
 require 'my_app' # Require the boot files for your app
-require 'provider_states_for_my_consumer' # See next section on setting up provider states
 
 Pact.service_provider "My Service Provider" do
   app { MyApp.new }
@@ -147,8 +168,31 @@ Pact.service_provider "My Service Provider" do
 end
 
 ```
+Require "pact/tasks" in your Rakefile. If the pact gem is in the test/development section of your Gemfile, you may want to put an env check around this so it doesn't load the pact tasks in prod.
+
+```ruby
+# In Rakefile
+
+require 'pact/tasks'
+```
+
+#### 3. Run your failing specs
+
+    $ rake pact:verify
+
+Congratulations! You now have a failing spec to develop against.
+
+#### 4. Implement your service provider
+
+At this stage, you'll probably want to be able to run your specs one at a time while you implement. Define the environment variables PACT_DESCRIPTION and/or PACT_PROVIDER_STATE as so:
+
+    $ PACT_DESCRIPTION="a request for something" PACT_PROVIDER_STATE="something exists" rake pact:verify
 
-#### Set up the service provider states
+#### 5. Keep going til you're green
+
+Yay! Your provider now honours the pact it has with your consumer. You can now have confidence that your consumer and provider will play nicely together.
+
+### Using provider states
 
 Having different service provider states allows you to test the same request with different expected responses.
 
@@ -161,6 +205,8 @@ my_service.
         with(method: 'get', path: '/thing').
           will_respond_with(status: 200, :body => {thing: "yay!"} )
 
+...
+
 my_service.
   given("a thing does not exist").
    upon_receiving("a request for a thing").
@@ -168,13 +214,11 @@ my_service.
         will_respond_with(status: 404, :body => {error: "There is no thing :("} )
 ```
 
-To define service provider states that create the right data for "a thing exists" and "a thing does not exist", write the following in the service provider project.
+To define service provider states that create the right data for "a thing exists" and "a thing does not exist", write the following in the service provider project. (The consumer name here must match the name of the consumer configured in your consumer project for it to correctly find these provider states.)
 
 
 ```ruby
-# The consumer name here must match the name of the consumer configured in your consumer project
-# for it to correctly find these provider states.
-# Make sure the provider states are included in or required by your pact_helper.rb file.
+# In /spec/service_consumers/provider_states_for_my_service_consumer.rb
 
 Pact.provider_states_for 'My Service Consumer' do
   provider_state "a thing exists" do
@@ -194,45 +238,46 @@ end
 
 ```
 
-If a state should be used for all consumers, the top level Pact.with_consumer can be skipped, and a global Pact.provider_state can be defined on its own.
-
-#### Verify that the service provider honours the pact
-
 ```ruby
-  # In your Rakefile
-  # If the pact gem is in the test/development section of your Gemfile, you may want to put an env check around this so it doesn't load the pact tasks in prod.
-  require 'pact/tasks'
-```
+# In /spec/service_consumers/pact_helper.rb
 
-```
-  $ rake -T
-  rake pact:verify               # Verifies the pact files configured in the pact_helper.rb against this service provider.
-  rake pact:verify:at[pact_uri]  # Verifies the pact at the given URI against this service provider.
-  $ rake pact:verify
+require_relative 'provider_states_for_my_service_consumer.rb'
 ```
 
-#### Verification using arbitrary pact files
+If a state should be used for all consumers, the top level Pact.with_consumer can be skipped, and a global Pact.provider_state can be defined on its own.
 
-```
-# Local URI
-$ rake pact:verify:at[../path-to-your-consumer-project/specs/pacts/my_consumer-my_provider.json]
 
-# Remote URI
-$ rake pact:verify:at[http://build-box/MyConsumerBuild/latestSuccessful/artifacts/my_consumer-my_provider.json]
-```
+### Verifying pacts
+
+You can verify a pact at an arbitrary local or remote URL
+
+    $ rake pact:verify:at[../path-to-your-consumer-project/specs/pacts/my_consumer-my_provider.json]
+    $ rake pact:verify:at[http://build-box/MyConsumerBuild/latestSuccessful/artifacts/my_consumer-my_provider.json]
 
-To make a shortcut task for pact at an arbitrary URI, add the following to your Rakefile.
+To make a shortcut task for pact at an arbitrary URL, add the following to your Rakefile. The pact.uri may be a local file system path or a remote URL.
 
 ```ruby
+# In Rakefile or /tasks/pact.rake
+
 # This creates a rake task that can be executed by running
-# $rake pact:verify:dev
+# $ rake pact:verify:dev
+
 Pact::VerificationTask.new(:dev) do | pact |
   pact.uri '../path-to-your-consumer-project/specs/pacts/my_consumer-my_provider.json'
 end
 ```
 
-The pact.uri may be a local file system path or a remote URL.
+### Configuration
 
+```ruby
+Pact.configure do | config |
+  config.pact_dir = "???" # Optional, default is ./spec/pacts
+  config.log_dir = "???" # Optional, default is ./log
+  config.logger = "??" # Optional, defaults to a file logger to the configured log_dir.
+  config.logger.level = Logger::DEBUG #By default this is INFO, bump this up to debug for more detailed logs
+  config.pactfile_write_mode = :ovewrite / :update / :smart # Optional. The default pactfile_write_mode is :overwrite. See notes in Advanced section for further information.
+end
+```
 
 ## Pact best practices
 
@@ -305,6 +350,32 @@ A pact service can be run locally and is really useful for debugging purposes.
 The service prints messages it recieves to stdout which can be really useful
 when diagnosing issues with pacts.
 
+### To run your consumer app as a process during your consumer specs
+
+Eg. for Capybara tests
+
+```ruby
+Pact.service_consumer "My Consumer" do
+  app my_consumer_rack_app
+  port 4321
+end
+```
+
+### Handling multiple headers with the same name
+
+RFC 2616 states that two headers with the same name can interpreted as a single header with two comma-separated values. This is the safest way to specify multiple headers with the same name, as Rack will only pass the last value through when they are defined separately (see https://github.com/rack/rack/issues/436).
+
+```ruby
+my_service_provider.
+  .given("it is RFC 2616 compliant")
+  .upon_receiving("a request with a header with commas separated values")
+  .with( method: :get, path: '/', headers: {'X-Request-Multival' => "A, B"} )
+  .will_respond_with(
+    status: 200, headers: {'X-Response-Multival' => "C, D"}
+  )
+
+```
+
 ### Pact file write mode
 
 By default, the pact file will be overwritten (started from scratch) every time any rspec runs any spec using pacts. This means that if there are interactions that haven't been executed in the most recent rspec run, they are effectively removed from the pact file. If you have long running pact specs (e.g. they are generated using the browser with Capybara) and you are developing both consumer and provider in parallel, or trying to fix a broken interaction, it can be tedius to run all the specs at once. In this scenario, you can set the pactfile_write_mode to :update. This will keep all existing interactions, and update only the changed ones, identified by description and provider state. The down side of this is that if either of those fields change, the old interactions will not be removed from the pact file. As a middle path, you can set pactfile_write_mode to :smart. This will use :overwrite mode when running rake (as determined by a call to system using 'ps') and :update when running an individual spec.

data/lib/pact/consumer/mock_service/rack_request_helper.rb

@@ -36,7 +36,7 @@ module Pact
       private
 
       def headers_from env
-        headers = env.reject{ |key, value| !(key.start_with?("HTTP") || key == 'CONTENT_TYPE')}
+        headers = env.reject{ |key, value| !(key.start_with?("HTTP") || key == 'CONTENT_TYPE' || key == 'CONTENT_LENGTH')}
         headers.inject({}) do | hash, header |
           hash[standardise_header(header.first)] = header.last
           hash

data/lib/pact/provider/client_project_pact_helper.rb

@@ -1,2 +1,4 @@
 require 'pact/provider/pact_helper_locator'
-load Pact::Provider::PactHelperLocater.pact_helper_path
+pact_helper_path = Pact::Provider::PactHelperLocater.pact_helper_path
+load pact_helper_path
+puts "Using #{pact_helper_path}"

data/lib/pact/provider/pact_spec_runner.rb

@@ -42,14 +42,13 @@ module Pact
 
       def require_pact_helper spec_definition
         if spec_definition[:pact_helper]
-          puts "Requiring #{spec_definition[:pact_helper]}"
+          puts "Using #{spec_definition[:pact_helper]}"
           require spec_definition[:pact_helper]
         elsif spec_definition[:support_file]
-          puts "Requiring #{spec_definition[:support_file]}"
+          puts "Using #{spec_definition[:support_file]}"
           $stderr.puts SUPPORT_FILE_DEPRECATION_MESSAGE
           require spec_definition[:support_file]
         else
-          puts "Requiring #{Pact::Provider::PactHelperLocater.pact_helper_path}"
           require 'pact/provider/client_project_pact_helper'
         end
       end

data/lib/pact/provider/request.rb

@@ -7,6 +7,9 @@ module Pact
     module Request
       class Replayable
 
+        # See https://github.com/rack/rack/blob/e7d741c6282ca4cf4e01506f5681e6e6b14c0b32/SPEC#L87-89
+        NO_HTTP_PREFIX = ["CONTENT-TYPE", "CONTENT-LENGTH"]
+
         def initialize expected_request
           @expected_request = expected_request
         end
@@ -32,12 +35,7 @@ module Pact
           request_headers = {}
           return request_headers if expected_request.headers.is_a?(Pact::NullExpectation)
           expected_request.headers.each do |key, value|
-            key = key.upcase
-            if key.match(/CONTENT.TYPE/)
-              request_headers['CONTENT_TYPE'] = value
-            else
-              request_headers[formatted_request_header_key(key)] = value
-            end
+            request_headers[rack_request_header_for(key)] = value
           end
           request_headers
         end
@@ -54,10 +52,19 @@ module Pact
           end
         end
 
-        def formatted_request_header_key(key)
-          'HTTP_' + key.to_s.gsub('-', '_')
+        def rack_request_header_for header
+          with_http_prefix(header.to_s.upcase).gsub('-', '_')
+        end
+
+        def rack_request_value_for value
+          Array(value).join("\n")
         end
-      end      
+
+        def with_http_prefix header
+          NO_HTTP_PREFIX.include?(header) ? header : "HTTP_#{header}"
+        end
+
+      end
     end
   end
 end

data/lib/pact/version.rb

@@ -1,3 +1,3 @@
 module Pact
-  VERSION = "1.0.20"
+  VERSION = "1.0.21"
 end

data/pact.gemspec

@@ -8,8 +8,8 @@ Gem::Specification.new do |gem|
   gem.version       = Pact::VERSION
   gem.authors       = ["James Fraser", "Sergei Matheson", "Brent Snook", "Ronald Holshausen", "Bethany Skurrie"]
   gem.email         = ["james.fraser@alumni.swinburne.edu", "sergei.matheson@gmail.com", "brent@fuglylogic.com", "uglyog@gmail.com", "bskurrie@dius.com.au"]
-  gem.description   = %q{Define a pact between service consumers and providers}
-  gem.summary       = %q{Define a pact between service consumers and providers}
+  gem.description   = %q{Enables consumer driven contract testing, providing a mock service and DSL for the consumer project, and interaction playback and verification for the service provider project.}
+  gem.summary       = %q{Enables consumer driven contract testing, providing a mock service and DSL for the consumer project, and interaction playback and verification for the service provider project.}
   gem.homepage      = "https://github.com/uglyog/pact.git"
 
   gem.files         = `git ls-files`.split($/)
@@ -24,8 +24,8 @@ Gem::Specification.new do |gem|
   gem.add_runtime_dependency 'rack-test', '~> 0.6.2'
   gem.add_runtime_dependency 'awesome_print', '~> 1.1.0'
   gem.add_runtime_dependency 'thor'
-  gem.add_runtime_dependency 'thin'
   gem.add_runtime_dependency 'json' #Not locking down a version because buncher gem requires 1.6, while other projects use 1.7.
+  gem.add_runtime_dependency 'webrick'
 
   gem.add_development_dependency 'rake', '~> 10.0.3'
   gem.add_development_dependency 'webmock', '~> 1.9.3'
@@ -34,6 +34,4 @@ Gem::Specification.new do |gem|
   gem.add_development_dependency 'hashie', '~> 2.0'
   gem.add_development_dependency 'rspec-fire'
   gem.add_development_dependency 'activesupport'
-  gem.add_development_dependency 'debugger'
-  gem.add_development_dependency 'geminabox-client'
 end

data/spec/integration/consumer_spec.rb

@@ -129,6 +129,40 @@ describe "A service consumer side of a pact", :pact => true  do
     end
   end
 
+  context "with multiple headers" do
+    before do
+      Pact.clear_configuration
+      Pact.service_consumer "Consumer" do
+        has_pact_with "Multi Headers Service" do
+          mock_service :multi_headers_service do
+            verify true
+            port 1240
+          end
+        end
+      end
+
+      multi_headers_service.
+        given("there are multiple headers").
+        upon_receiving("a request with multiple headers").
+        with(method: :get, path: '/something', headers: {'X-Something' => "1, 2"}).
+        will_respond_with(status: 200)
+    end
+
+    it "handles multiple headers with the same name in a comma separated list" do
+        interactions = Pact::ConsumerContract.from_json(File.read(multi_headers_service.consumer_contract.pactfile_path)).interactions
+        expect(interactions.first.request.headers['X-Something']).to eq("1, 2")
+
+        uri = URI('http://localhost:1240/something')
+        post_req = Net::HTTP::Get.new(uri.path)
+        post_req.add_field('X-Something', '1')
+        post_req.add_field('X-Something', '2')
+        response = Net::HTTP.start(uri.hostname, uri.port) do |http|
+          http.request post_req
+        end
+    end
+
+  end
+
   context "with a async interaction with provider" do
     before do
       Pact.clear_configuration

data/spec/lib/pact/consumer/mock_service/rack_request_helper_spec.rb

@@ -27,6 +27,7 @@ module Pact::Consumer
                 "HTTP_ACCEPT" => "text/plain",
             "HTTP_USER_AGENT" => "Ruby",
                   "HTTP_HOST" => "localhost:4321",
+           "HTTP_X_SOMETHING" => "1, 2",
                "rack.version" => [1, 2 ],
                  "rack.input" => StringIO.new(body),
                 "rack.errors" => nil,
@@ -39,6 +40,9 @@ module Pact::Consumer
       }
      }
 
+     let(:content_type) { "" }
+     let(:body) { '' }
+
     subject { TestSubject.new }
 
     let(:expected_request) {
@@ -49,10 +53,12 @@ module Pact::Consumer
              :path => "/donuts",
           :headers => {
               "Content-Type" => content_type,
+              "Content-Length" => "16",
                     "Accept" => "text/plain",
                 "User-Agent" => "Ruby",
                       "Host" => "localhost:4321",
-                   "Version" => "HTTP/1.1"
+                   "Version" => "HTTP/1.1",
+                   "X-Something" => "1, 2"
           }
       }
     }

data/spec/lib/pact/provider/request_spec.rb

@@ -6,10 +6,10 @@ describe Pact::Provider::Request::Replayable do
   let(:path) { '/path?something' }
   let(:body) { {a: 'body'} }
   let(:headers) { {} }
-  let(:expected_request) do 
-    instance_double('Pact::Request::Expected', 
-      :method => 'post', 
-      :full_path => path, 
+  let(:expected_request) do
+    instance_double('Pact::Request::Expected',
+      :method => 'post',
+      :full_path => path,
       :body => body,
       :headers => headers)
   end
@@ -62,8 +62,8 @@ describe Pact::Provider::Request::Replayable do
 
   describe "headers" do
     context "when headers are expected" do
-      let(:headers) { {"Content-Type" => "text/plain", "Accept" => "application/json", "Access-Control-Request-Method" => "POST"} }
-      let(:expected_headers) { {"CONTENT_TYPE" => "text/plain", "HTTP_ACCEPT" => "application/json", "HTTP_ACCESS_CONTROL_REQUEST_METHOD" => "POST"} }
+      let(:headers) { {"Content-Type" => "text/plain", "Content-Length" => "123", "X-Content-Type" => "special", "Access-Control-Request-Method" => "POST"} }
+      let(:expected_headers) { {"CONTENT_TYPE" => "text/plain", "CONTENT_LENGTH" => "123", "HTTP_ACCESS_CONTROL_REQUEST_METHOD" => "POST", "HTTP_X_CONTENT_TYPE" => "special"} }
       it "transforms the headers into Rack format" do
         expect(subject.headers).to eq( expected_headers )
       end

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: pact
 version: !ruby/object:Gem::Version
-  version: 1.0.20
+  version: 1.0.21
   prerelease: 
 platform: ruby
 authors:
@@ -13,7 +13,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-10-30 00:00:00.000000000 Z
+date: 2013-11-25 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: randexp
@@ -112,7 +112,7 @@ dependencies:
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
-  name: thin
+  name: json
   requirement: !ruby/object:Gem::Requirement
     none: false
     requirements:
@@ -128,7 +128,7 @@ dependencies:
       - !ruby/object:Gem::Version
         version: '0'
 - !ruby/object:Gem::Dependency
-  name: json
+  name: webrick
   requirement: !ruby/object:Gem::Requirement
     none: false
     requirements:
@@ -255,39 +255,9 @@ dependencies:
     - - ! '>='
       - !ruby/object:Gem::Version
         version: '0'
-- !ruby/object:Gem::Dependency
-  name: debugger
-  requirement: !ruby/object:Gem::Requirement
-    none: false
-    requirements:
-    - - ! '>='
-      - !ruby/object:Gem::Version
-        version: '0'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    none: false
-    requirements:
-    - - ! '>='
-      - !ruby/object:Gem::Version
-        version: '0'
-- !ruby/object:Gem::Dependency
-  name: geminabox-client
-  requirement: !ruby/object:Gem::Requirement
-    none: false
-    requirements:
-    - - ! '>='
-      - !ruby/object:Gem::Version
-        version: '0'
-  type: :development
-  prerelease: false
-  version_requirements: !ruby/object:Gem::Requirement
-    none: false
-    requirements:
-    - - ! '>='
-      - !ruby/object:Gem::Version
-        version: '0'
-description: Define a pact between service consumers and providers
+description: Enables consumer driven contract testing, providing a mock service and
+  DSL for the consumer project, and interaction playback and verification for the
+  service provider project.
 email:
 - james.fraser@alumni.swinburne.edu
 - sergei.matheson@gmail.com
@@ -301,6 +271,7 @@ extra_rdoc_files: []
 files:
 - .gitignore
 - .rspec
+- .travis.yml
 - CHANGELOG.md
 - Gemfile
 - Gemfile.lock
@@ -448,7 +419,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
       version: '0'
       segments:
       - 0
-      hash: -2921179149528665156
+      hash: -2335732393810580306
 required_rubygems_version: !ruby/object:Gem::Requirement
   none: false
   requirements:
@@ -457,13 +428,15 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
       segments:
       - 0
-      hash: -2921179149528665156
+      hash: -2335732393810580306
 requirements: []
 rubyforge_project: 
 rubygems_version: 1.8.23
 signing_key: 
 specification_version: 3
-summary: Define a pact between service consumers and providers
+summary: Enables consumer driven contract testing, providing a mock service and DSL
+  for the consumer project, and interaction playback and verification for the service
+  provider project.
 test_files:
 - spec/features/consumption_spec.rb
 - spec/features/production_spec.rb