Verifying a Pact JSON with Headers and Flexible Matching

[hugomd]

Hi,

I've been having troubles with headers, which I've managed to fix, but flexible matching, specifically regular expressions, doesn't seem to be working at all. Could someone shed some light on this? Am I using the wrong implementation of Pact for verification?

Thanks,

[uglyog]

Can you provide more details of your problem? Pact version, build tool and debug log file from the verification test?

[uglyog]

It could be that regular expressions are not implemented for headers, only for the body.

[hugomd]

@uglyog Thanks for the response!

I'm using Pact-Consumer-JS-DSL to generate the pact that I've written in Jasmine, and Pact Mock Service version 0.7.0.

My issues are:

• I have an authorization header that uses a JWT, and I can't work out how to use that with Jasmine..
• I'm using pactjs0 to verify the contract against an actual in-use API - and I don't know if I should be using that or something else for verification?

Regex isn't working at all in pactjs0, and it seems outdated.. What should I be using?

[uglyog]

pactjs0 was just a spike, so is not very feature complete. There is a initiative to build a JavaScript implementation for verifying pacts, but it is still in the inception phase.

The Pact Mock Service does support matching on headers, so I would either use the Ruby pact provider proxy (https://github.com/bethesque/pact-provider-proxy) or one of the JVM build plugins (https://github.com/DiUS/pact-jvm#service-providers) to verify against your running API. Depends on whether you like having Ruby or the JVM as a dependency.

[mefellows]

Hi @hugomd, at Seek, we used Docker to achieve what @uglyog has mentioned - this saved us from the mess of having to worry about all of the languages (Node, Ruby/JVM).

I have just pushed up an example at https://github.com/DiUS/pact-provider-verifier-docker which hopefully we can formalise further and publish to the Registry soon.

It might be worth taking a look at that for some inspiration