When Pact fails, it's a bit hard to know what the issue is considering the requests are not being printed back to the terminal. At the moment, I'm using this custom method to do this but I think it would be nice to have something like this out of the box.

public static void logCurlFromPact(PactVerificationContext context, HttpRequest request) {

        String bodyParam = ((RequestRespon

Currently, this is indicated using colour only, which is unhelpful if you are red/green colourblind.

The README still has a link to this old workshop, which is quite outdated relative to the current status of this project.

Ideally, this workshop is updated to reflect the latest/greatest things.

Should we (in the mean time) remove the link?

See also DiUS/pact-workshop-dotnet-core-v3#1 (comment)

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

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

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

❕ 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

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