bethesque

# gem "omniauth-github"
# gem "rack-rewrite"

require 'fileutils'
require 'logger'
require 'sequel'
require 'pact_broker'
require 'omniauth/strategies/github'
require 'rack/rewrite'

bethesque

require 'pact/provider/proxy/tasks'

Pact::ProxyVerificationTask.new :userapi_service do | task |
  task.pact_url './spec/pacts/userapi_service_consumer-userapi_service_provider.json'
  task.provider_base_url 'https://userapi.com/'
end

Pact::ProxyVerificationTask.new :otherapi_service do | task |
  task.pact_url './spec/pacts/otherapi_service_consumer-otherapi_service_provider.json'
  task.provider_base_url 'https://otherapi.com'

bethesque

source 'https://rubygems.org'

gem 'pact', '~>1.7.0'

bethesque

When you declare a request and response using the traditional Pact DSL, ("uponReceiving" and "willRespondWith") you're building a structure that has three purposes -

1. it provides the concrete example request and response used in the tests
2. it specifies the contents of the contract which...
3. defines how to validate the the actual request/response against the expected request/response

The three different uses of this structure are hidden from you when using HTTP Pact because the mock service handles numbers 1 & 2 in the consumer tests, and the verification task handles number 3 for you in the provider tests. When using Pact in a non-HTTP scenario, there is no nice neat protocol layer to inject the code to do this for you, so you have to explicitly do each step.

The file expected_data_from_collector.rb declares an object graph using the Pact DSL. This is going to be used to create the concrete example and the contract. This could be declared inline, but for easier maintenance, and to allow the contr

bethesque

# Note: this does not migrate the tags

require 'faraday'
require 'json'

source_host = 'http://some-pact-broker'
destination_host = 'http://localhost:9292'

latest_pacts_response = JSON.parse(Faraday.get("#{source_host}/pacts/latest").body)
pact_hrefs = latest_pacts_response['pacts'].collect{ | pact | pact['_links']['self'][1]['href'] }

bethesque

# pact-provider-proxy/vendor/rack-reverse-proxy/lib/rack/reverse_proxy.rb

require 'net/http'
require 'net/https'
require "rack-proxy"
require "rack/reverse_proxy_matcher"
require "rack/exception"

module Rack
  class ReverseProxy

bethesque

class Thing::Create < Trailblazer::Operation

  def process(params)
    validate(params[:referral]) do
      authorize(params, model, :create?) 
      form.save
    end
  end

  def setup_model!(params)

bethesque

This allows you do something like:

User = Struct.new(:address)
Address = Struct.new(:street, :suburb)

class UserForm < Reform::Form

  property :address do
 property :street

bethesque

https://github.com/realestate-com-au/pact - rpsec specific stuff, top level, executables https://github.com/bethesque/pact-mock_service - standalone, used by javascript, starts up service, listens, writes pact, verification https://github.com/bethesque/pact-support - matching logic, domain objects https://github.com/bethesque/pact-support/blob/master/spec/pact_specification/compliance-2.0.rb - pact specification test, people might want version 3 soonish.

https://github.com/bethesque/pact-mock-service-npm - standalone package using travelling ruby https://github.com/bethesque/pact-mock_service/blob/master/tasks/package.rake - this is the task that builds the packages

https://github.com/DiUS/pact-consumer-js-dsl - the javascript DSL that wraps the ruby or standalone mock server.

bethesque

This will sort based on the date that the consumer application version resource is created. 
If the pact for that version is updated, the sorting will not consider the date of the updated content.