Extending a Pact

[what-is-a-crow]

We're using pact to allow our mobile app development team to define their expectations of our API; they're creating JSON-based pacts via the Swift consumer library. The problem is that our API uses token-based authentication, which works off of request headers (which are fixed in the JSON files).

Would it be possible to extend a pact programmatically so as to allow for more realistic end-to-end testing (without stubbing out the backend)? I would imagine the API would look something like so:

Pact.provider_states_for "iOS" do
  set_up do |provider_state|
    provider_state.request.headers["Authentication"] = "foo"
  end
end

[bethesque]

It's something we've thought about, but have always managed to find a way to work around. I'm a little hesitant to add it, but can see why it would be useful.

How are you verifying the provider at the moment? Using pact-provider-proxy to verify against a running server, or running it against a normal Rack app?

[what-is-a-crow]

We're running against a normal Rack app.

On Mon, Jul 20, 2015 at 6:45 PM, Beth Skurrie notifications@github.com
wrote:

It's something we've thought about, but have always managed to find a way to work around. I'm a little hesitant to add it, but can see why it would be useful.

How are you verifying the provider at the moment? Using pact-provider-proxy to verify against a running server, or running it against a normal Rack app?

Reply to this email directly or view it on GitHub:
https://github.com/realestate-com-au/pact/issues/84#issuecomment-123078433

[bethesque]

In that case, you can do a quick and dirty trick using some Rack middleware.

class ProxyRackApp
  def initialize app
    @app = app
  end

  def call env
    # Modify headers here!
    @app.call(env)
  end
end

Pact.service_provider "My provider" do
  app { ProxyRackApp.new(your_provider_app) }
end

[bethesque]

Closing, assuming this helped.