Comments (6)
Initial models to support this have been added to Pact-Rust. Sample JSON file format:
{
"consumer": {
"name": "consumer"
},
"interactions": [
{
"description": "Test Interaction",
"key": "a0395223ce6c542b",
"providerStates": [
{
"name": "Good state to be in"
}
],
"request": {
"description": "Request Message",
"key": "eb97728e3ed8475f",
"contents": {
"contentType": "application/json",
"encoded": false,
"content": {
"a": "1234-1234"
}
},
"type": "Asynchronous/Messages"
},
"response": [
{
"description": "Message Response",
"key": "eb97728e3ed8475f",
"contents": {
"contentType": "application/json",
"encoded": false,
"content": {
"a": "1234-1234"
}
},
"type": "Asynchronous/Messages"
}
],
"type": "Synchronous/Messages"
}
],
"metadata": {
"pactSpecification": {
"version": "4.0"
}
},
"provider": {
"name": "write_pact_test_provider"
}
}
from pact-specification.
What does the key do?
from pact-specification.
What does the key do?
from pact-specification.
Sweet!
from pact-specification.
I can't see this documented here https://github.com/pact-foundation/pact-specification/tree/version-4 Ron, should it be there now also?
from pact-specification.
Now documented in the main readme
from pact-specification.
Related Issues (20)
- Events driven architecture like aws event bridge contract testing HOT 1
- Feature Request - eachLike(itemDescriptionWithMatchers, exampleArray?) HOT 4
- Definitive word on PACT and HATEOAS HOT 1
- V4 Pact Specification Metadata format changed HOT 3
- Guidance and documentation needed to differentiate between event messages and command messages? HOT 1
- Pending pacts and can-i-deploy HOT 5
- Option to check for no undeclared fields HOT 3
- Generated pact file body include json_class, contents information and doesn't have matchingRules section HOT 2
- V4: add a boolean matcher
- Matchers don't work with SSE response format HOT 1
- Question: providerStates allowed in any contract? HOT 1
- Type of regular expressions used in pact HOT 2
- How to match xml elements with namespace ? HOT 3
- Serialisation of ProviderStateGenerator HOT 2
- Add number range matcher
- json schema for version 3 pact files HOT 2
- The V4 Specification Retrospectively Alters the V3 Specification for Matchers and Generators HOT 6
- Either matcher in Pact HOT 2
- Convert PACT file to OAS 3.0 file HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from pact-specification.