Please add support for the following keys to be used in the consumer version selectors when fetching pacts for verification:

{ "deployedOrReleased": true }

{ "deployed": true }

{ "released": true }

{ "environment": "<env name>" }

{ "consumer": "<name>" } // this may already be supported, please add it if not

These keys can be used in various combinations ( eg. `{ "envir

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

The fastapi example (and perhaps the others) are a little misleading to newbies.

The following lines would suggest that there is pact mock on the provider side, when in reality this is the address of the locally running FastAPI provider:

PACT_MOCK_HOST = 'loca

Hi, I'm trying to add a custom header, but it seems that if it's not defined it will not add it
please see comments on code...

import { PostmanMappedOperation } from '../../postman'
import { OverwriteRequestHeadersConfig } from '../../types'

/**
 * Overwrite Postman request headers with values defined by the portman testsuite
 * @param overwriteValues
 * @param pmOperati

Please add support for the following keys to be used in the consumer version selectors when fetching pacts for verification:

{ "deployedOrReleased": true }

{ "deployed": true }

{ "released": true }

{ "environment": "<env name>" }

{ "consumer": "<name>" } // this may already be supported, please add it if not

These keys can be used in various combinations ( eg. `{ "envir

Describe the bug
Most expect methods print the request and response when the assertion fails.
However, the custom expect handler does not show these objects.

To Reproduce
Steps to reproduce the behavior:

const spec = pactum.spec();
spec.get(url);
await spec.toss();
await spec.response().to.have._((ctx) => {
  assert.fail('error');
});

*Expected behavior

Description
When the file passed to the stub does not exist, the stub neither displays an error nor exits.

Steps to reproduce

1. Run the command qontract stub nonexistent.qontract
2. Qontract runs, but prints nothing, nor does it exit.

Expected behavior
If any of the files or directories provided do not exist, Qontract should highlight this, but it should not die if there is

❕ Problem Statement

Provide resources to help new users become proficient in Pact and PactSwift

💬 Task Description

Create an end-to-end workshop based on the canonical pact one (https://github.com/pact-foundation/pact-workshop-js).

👩‍🔧 Technical Design Notes

Suggest using the JS provider as the "backend" for the workshop, to both reduce the effort required in this workshop and

In order to test soap like api's (using XML for their body) a gandalf.pathing.Extractor that supports XPath is required.