spring-cloud-contract icon indicating copy to clipboard operation
spring-cloud-contract copied to clipboard

Support for Consumer Driven Contracts in Spring

Results 115 spring-cloud-contract issues
Sort by recently updated
recently updated
newest added

Currently, we support 3 different combinations of messaging contracts (-> means a message is sent). Let's say that we store contracts on the producer side. Our producer is service called...

enhancement
help wanted
breaking change

Hi, In some scenarios, native developments like Android/IOS could be considered like other Consumers from `Contract testing` perspective for a REST API. Using `Spring cloud contract` is possible to run...

help wanted

Enhancement. Hi everyone! I'd like to suggest a feature to add DSL classes for easy SOAP contracts writing and providing a convenient standard. SOAP looks like the standard HTTP synchronous...

help wanted
documentation

Hi, Currently `spring-cloud-contract` supports this test matrix: []() | Consumer Head | Consumer Prod --- | ---------------- | ---------------- **Producer Head** | Ok | Ok (ensure provider is backwards compatible)...

enhancement
help wanted

Improve build experience with Gradle plugin by supporting Gradle build cache. https://guides.gradle.org/using-build-cache/ Note: there is also the Gradle build cache for Maven which might be feasible, but I'm not as...

enhancement

Add possibility to define and verify input and output messages with XML body. This is an issue created to verify if there is any interest in this functionality for messaging....

enhancement
icebox

With `RequestMatcherExtension` we could consider allowing giving the users the option to pass in their own, custom matching options. Sth like this: ```java class DefaultRequestMatcher extends RequestMatcherExtension { private static...

enhancement
help wanted

In contract, if we have two array items and we are trying to validate both with same regex in our request, as of now, if any of the two gets...

enhancement
help wanted

Spring Cloud Contract Wiremock supports generating `bodyMatchers` for request when the contract is created using Spring RestDocs. However, the same is not possible for response ([see here](https://github.com/spring-cloud/spring-cloud-contract/blob/master/spring-cloud-contract-wiremock/src/main/java/org/springframework/cloud/contract/wiremock/restdocs/ContractDslSnippet.java#L80)). I think this...

enhancement
help wanted