Support matchers and example generators in requests #113
Labels
enhancement
New feature or request
help wanted
Extra attention is needed
v2.x.x
Tasks related to setting up next major version of PactSwift
Uh oh!
There was an error while loading. Please reload this page.
🗣 Context
Setting expectations for requests should be as strict as possible since we own the code and own the data to verify our system's behaviour - Choosing the right type of matching.
But sometimes when sending requests, specifically
POST
requests, sometimes we need to generate a random value and send to the provider. This can be an issue when we want to verify thekey
is being sent, but we can't guarantee the value to be sent.📝 Notes
Branch off of https://github.com/surpher/PactSwift/tree/feat/v2.0.0
💬 Narrative
When setting up expectations for requests
I want to be able to use matchers
So that requests don't fail when generated values are being sent
🏗 Design
✅ Acceptance Criteria
GIVEN defining expectations for requests
WHEN matchers and/or example generators are used
THEN they are reflected in the Pact contract
and considered when verifying the interactions (running Pact test) (eg: request doesn't fail if expected uuid doesn't match the sent uuid)
🚫 Out of Scope
N/A
The text was updated successfully, but these errors were encountered: