Before becoming Spring Cloud Contract, this project was called Accurest. It was created by Marcin Grzejszczak and Jakub Kubrynski -from (codearte.io.
+from (Codearte.The 0.1.0 release took place on 26 Jan 2015 and it became stable with 1.0.0 release on 29 Feb 2016.
fraud. That gives you the FraudBase test cl
All the generated tests extend that class. Over there, you can set up your Spring Context
-or whatever is necessary. In this case, use Rest Assured MVC to
+or whatever is necessary. In this case, use Rest Assured MVC to
start the server side FraudDetectionController.
mvn clean install -DskipTests to install locally the stubs
com.example:foo:1.0.0
3.7. Can I use the Pact Broker?
-When using Pact you can use the Pact Broker
+
When using Pact you can use the Pact Broker
to store and share Pact definitions. Starting from Spring Cloud Contract
2.0.0 one can fetch Pact files from the Pact Broker to generate
tests and stubs.
@@ -4000,7 +4000,7 @@ Gradle or a Maven plugin.
If you want to use Spock in your projects, you must add separately the
-spock-core and spock-spring modules. Check Spock
+spock-core and spock-spring modules. Check Spock
docs for more information
@@ -5359,7 +5359,7 @@ name of scenario1 and the three following steps:
More details about WireMock scenarios can be found at
-http://wiremock.org/docs/stateful-behaviour/
+https://wiremock.org/docs/stateful-behaviour/
Spring Cloud Contract Verifier also generates tests with a guaranteed order of execution.
@@ -5438,7 +5438,7 @@ like them to be available for others to download / reference or reuse. In case
of the JVM world those artifacts would be JARs, for Ruby these are gems
and for Docker those would be Docker images. You can store those artifacts
in a manager. Examples of such managers can be Artifactory
-or Nexus.
+or Nexus.
@@ -5464,7 +5464,7 @@ purposes).
execute the tests against the provided URL
-generate the WireMock stubs
+generate the WireMock stubs
(optional - turned on by default) publish the stubs to a Artifact Manager
@@ -6371,7 +6371,7 @@ publishing {
6.3. Stub Runner Core
Runs stubs for service collaborators. Treating stubs as contracts of services allows to use stub-runner as an implementation of
-Consumer Driven Contracts.
+Consumer Driven Contracts.
Stub Runner allows you to automatically download the stubs of the provided dependencies (or pick those from the classpath), start WireMock servers for them and feed them with proper stub definitions.
@@ -6422,7 +6422,7 @@ For messaging, special stub routes are defined.
-@AutoConfigureStubRunner(repositoryRoot="http://foo.bar", ids = "com.example:beer-api-producer:+:stubs:8095", stubsMode = StubRunnerProperties.StubsMode.LOCAL)
+@AutoConfigureStubRunner(repositoryRoot="https://foo.bar", ids = "com.example:beer-api-producer:+:stubs:8095", stubsMode = StubRunnerProperties.StubsMode.LOCAL)
Starting from 1.4.0.RELEASE version of the Spring Cloud CLI
+
Starting from 1.4.0.RELEASE version of the Spring Cloud CLI
project you can start Stub Runner Boot by executing spring cloud stubrunner.
@AutoConfigureStubRu
* -Dstubrunner.repositoryRoot=https://repo.spring.io/snapshots (1)
+* -Dstubrunner.repositoryRoot=https://repo.spring.io/snapshot (1)
* -Dstubrunner.cloud.stubbed.discovery.enabled=false (2)
* -Dstubrunner.ids=org.springframework.cloud.contract.verifier.stubs:loanIssuance,org.
* springframework.cloud.contract.verifier.stubs:fraudDetectionServer,org.springframework.
@@ -10520,7 +10520,7 @@ optional parameters only for the following:
}
body(
email: $(consumer(optional(regex(email()))), producer('abc@abc.com')),
- callback_url: $(consumer(regex(hostname())), producer('http://partners.com'))
+ callback_url: $(consumer(regex(hostname())), producer('https://partners.com'))
)
}
response {
@@ -10548,7 +10548,7 @@ expression that must be present 0 or more times.
given:
def request = given()
.header("Content-Type", "application/json")
- .body('''{"email":"abc@abc.com","callback_url":"http://partners.com"}''')
+ .body('''{"email":"abc@abc.com","callback_url":"https://partners.com"}''')
when:
def response = given().spec(request)
@@ -10803,7 +10803,7 @@ matches the JSON Path.
If you’re using the YAML contract definition you have to use the
-Handlebars {{{ }}} notation with custom, Spring Cloud Contract
+Handlebars {{{ }}} notation with custom, Spring Cloud Contract
functions to achieve this.
The Spring Cloud Contract WireMock modules let you use WireMock in a +
The Spring Cloud Contract WireMock modules let you use WireMock in a Spring Boot application. Check out the samples for more details.
@@ -14276,7 +14276,7 @@ public class WiremockForDocsMockServerApplicationTests { public void contextLoads() throws Exception { // will read stubs classpath MockRestServiceServer server = WireMockRestServiceServer.with(this.restTemplate) - .baseUrl("http://example.org").stubs("classpath:/stubs/resource.json") + .baseUrl("https://example.org").stubs("classpath:/stubs/resource.json") .build(); // We're asserting if WireMock responded properly assertThat(this.service.go()).isEqualTo("Hello World"); @@ -14290,11 +14290,11 @@ public class WiremockForDocsMockServerApplicationTests {The baseUrl value is prepended to all mock calls, and the stubs() method takes a stub
path resource pattern as an argument. In the preceding example, the stub defined at
/stubs/resource.json is loaded into the mock server. If the RestTemplate is asked to
-visit http://example.org/, it gets the responses as being declared at that URL. More
+visit https://example.org/, it gets the responses as being declared at that URL. More
than one stub pattern can be specified, and each one can be a directory (for a recursive
list of all ".json"), a fixed filename (as in the example above), or an Ant-style
pattern. The JSON format is the normal WireMock format, which you can read about in the
-WireMock website.
Currently, the Spring Cloud Contract Verifier supports Tomcat, Jetty, and Undertow as @@ -14692,7 +14692,7 @@ structure presented in the previous snippet.
<assembly xmlns="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.3" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" - xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.3 http://maven.apache.org/xsd/assembly-1.1.3.xsd"> + xsi:schemaLocation="http://maven.apache.org/plugins/maven-assembly-plugin/assembly/1.1.3 https://maven.apache.org/xsd/assembly-1.1.3.xsd"> <id>stubs</id> <formats> <format>jar</format>