In a pact-node consumer test, I have -

describe('edit a policy', () => {
    const REQUEST_BODY = {
      name: 'account-holder',
      version: '2020-07-10T01:22:09.488Z',
    };
    const RESPONSE_BODY = {
      name: Matchers.like('account-holder'),
      version: Matchers.ISO8601_DATETIME_WITH_MILLIS_FORMAT,
      additionalAttributes: Matchers.like({}),
    };
    beforeEach(

If there's a single/small number of points to put this code so that it worked for all calls, that would be great. One can dream...

If there is not, there are two main use cases that crop up frequently that it would be great to cover.

Print the body when there is a 401 response received from Pactflow. There is text in the error response that helps users with incorrectly configured credentials

As part of the process of making the Pact docs more user friendly, we'd like to start writing feature documentation once, and providing code examples for each of the languages, rather than everyone having to write the same docs over and over again in each language.

The documentation for the consumer version selectors can be our first opportunity to give this approach a try. I have written the beh

As part of the process of making the Pact docs more user friendly, we'd like to start writing feature documentation once, and providing code examples for each of the languages, rather than everyone having to write the same docs over and over again in each language.

The documentation for the consumer version selectors can be our first opportunity to give this approach a try. I have written the beh

enforce is currently strict in the error message, which means that e.g. using format to make an informative error is expensive even if the test passes.

-Dpact.rootDir="target/pact-classes" didn’t work for me.
env "pact.rootDir=target/pact-classes" bash did

...because of the "."