You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the use case that motivates this feature request?
Reuse of pacts for consumer development/testing while utilizing the pact-stub-server Please describe why you would like Pact-js to have this feature.
We have a consumer (react ui) pact we would like to reuse as a stub response within a real network request by loading our pacts into thepactfoundation/pact-stub-server. This benefits us in two specific ways:
We're able to reuse our pacts for a small set of integration tests with the provider apis
We're able to reuse our pacts for local development purposes of react ui and not be connected to a provider backend.
Our goal is to generate a realistic response to reuse during development/testing and also be minimalistic for the provider to verify, eg atLeastOneLike.
Request for matcher(s) to support eachLike(matcher, exampleArray?), atLeastOneLike(matcher, exampleArray?) so that the generated stub response for the consumer definition is:
Checklist
This checklist is optional, but studies show that people who have followed it checklist are really excellent people and we like them 🤣
Before making a feature request, I have:
Feature description
Please describe what you would like Pact-js to do
Extended support for matching arrays with an optional example parameter, such as:
Use case
What is the use case that motivates this feature request?
Reuse of pacts for consumer development/testing while utilizing the pact-stub-server
Please describe why you would like Pact-js to have this feature.
We have a consumer (react ui) pact we would like to reuse as a stub response within a real network request by loading our pacts into the
pactfoundation/pact-stub-server
. This benefits us in two specific ways:Our goal is to generate a realistic response to reuse during development/testing and also be minimalistic for the provider to verify, eg atLeastOneLike.
Request for matcher(s) to support
eachLike(matcher, exampleArray?), atLeastOneLike(matcher, exampleArray?)
so that the generated stub response for the consumer definition is:and the generated matcher for the provider is:
Additional discussion here pact-foundation.slack.com/#general
The text was updated successfully, but these errors were encountered: