From af9d46b65d9cfbb24e2d72a4c544d7d18a0627db Mon Sep 17 00:00:00 2001 From: buildmaster Date: Thu, 19 Oct 2017 12:57:47 +0000 Subject: [PATCH] Sync docs from master to gh-pages --- multi/multi__contract_dsl.html | 7 +++++-- multi/multi_spring-cloud-contract.html | 2 +- single/spring-cloud-contract.html | 9 ++++++--- spring-cloud-contract.xml | 10 ++++++++++ 4 files changed, 22 insertions(+), 6 deletions(-) diff --git a/multi/multi__contract_dsl.html b/multi/multi__contract_dsl.html index 7549b8bc91..81eb63a967 100644 --- a/multi/multi__contract_dsl.html +++ b/multi/multi__contract_dsl.html @@ -1053,7 +1053,7 @@ socket.

Consider the following contract:

or
 }

If you do it this way:

7.9 Messaging Top-Level Elements

The DSL for messaging looks a little bit different than the one that focuses on HTTP. The -following sections explain the differences:

7.9.1 Output Triggered by a Method

The output message can be triggered by calling a method (such as a Scheduler when a was +following sections explain the differences:

7.9.1 Output Triggered by a Method

The output message can be triggered by calling a method (such as a Scheduler when a was started and a message was sent), as shown in the following example:

def dsl = Contract.make {
 	// Human readable description
 	description 'Some description'
@@ -1129,7 +1129,10 @@ parts):
Contract.make {
 				bookName: 'foo'
 		])
 	}
-}

7.10 Multiple Contracts in One File

You can define multiple contracts in one file. Such a contract might resemble the +}

7.9.4 Common

In the input {} or outputMessage {} section you can call assertThat with the name +of a method (e.g. assertThatMessageIsOnTheQueue()) that you have defined in the +base class or in a static import. Spring Cloud Pipelines will execute that method +in the genertaed test.

7.10 Multiple Contracts in One File

You can define multiple contracts in one file. Such a contract might resemble the following example:

import org.springframework.cloud.contract.spec.Contract
 
 [
diff --git a/multi/multi_spring-cloud-contract.html b/multi/multi_spring-cloud-contract.html
index f2a22280f8..c5c9c65e4b 100644
--- a/multi/multi_spring-cloud-contract.html
+++ b/multi/multi_spring-cloud-contract.html
@@ -1,3 +1,3 @@
 
       
-   Spring Cloud Contract
Spring Cloud Contract
   Next
Spring Cloud Contract
Table of Contents
1. Spring Cloud Contract
2. Spring Cloud Contract Verifier Introduction
2.1. Why a Contract Verifier?
2.1.1. Testing issues
2.2. Purposes
2.3. How It Works
2.3.1. Defining the contract
2.3.2. Client Side
2.3.3. Server Side
2.4. Step-by-step Guide to Consumer Driven Contracts (CDC)
2.4.1. Technical note
2.4.2. Consumer side (Loan Issuance)
2.4.3. Producer side (Fraud Detection server)
2.4.4. Consumer Side (Loan Issuance) Final Step
2.5. Dependencies
2.6. Additional Links
2.6.1. Spring Cloud Contract video
2.6.2. Readings
2.7. Samples
3. Spring Cloud Contract Verifier Setup
3.1. Gradle Project
3.1.1. Prerequisites
3.1.2. Add Gradle Plugin with Dependencies
3.1.3. Gradle and Rest Assured 2.0
3.1.4. Snapshot Versions for Gradle
3.1.5. Add stubs
3.1.6. Run the Plugin
3.1.7. Default Setup
3.1.8. Configure Plugin
3.1.9. Configuration Options
3.1.10. Single Base Class for All Tests
3.1.11. Different Base Classes for Contracts
3.1.12. Invoking Generated Tests
3.1.13. Spring Cloud Contract Verifier on the Consumer Side
3.2. Maven Project
3.2.1. Add maven plugin
3.2.2. Maven and Rest Assured 2.0
3.2.3. Snapshot versions for Maven
3.2.4. Add stubs
3.2.5. Run plugin
3.2.6. Configure plugin
3.2.7. Configuration Options
3.2.8. Single Base Class for All Tests
3.2.9. Different base classes for contracts
3.2.10. Invoking generated tests
3.2.11. Maven Plugin and STS
3.2.12. Spring Cloud Contract Verifier on the Consumer Side
3.3. Stubs and Transitive Dependencies
3.4. Scenarios
4. Spring Cloud Contract Verifier Messaging
4.1. Integrations
4.2. Manual Integration Testing
4.3. Publisher-Side Test Generation
4.3.1. Scenario 1: No Input Message
4.3.2. Scenario 2: Output Triggered by Input
4.3.3. Scenario 3: No Output Message
4.4. Consumer Stub Generation
5. Spring Cloud Contract Stub Runner
5.1. Snapshot versions
5.2. Publishing Stubs as JARs
5.3. Stub Runner Core
5.3.1. Retrieving stubs
Stub downloading
Classpath scanning
5.3.2. Running stubs
Limitations
Running using main app
HTTP Stubs
Viewing registered mappings
Messaging Stubs
5.4. Stub Runner JUnit Rule
5.4.1. Maven settings
5.4.2. Providing fixed ports
5.4.3. Fluent API
5.4.4. Stub Runner with Spring
5.5. Stub Runner Spring Cloud
5.5.1. Stubbing Service Discovery
Test profiles and service discovery
5.5.2. Additional Configuration
5.6. Stub Runner Boot Application
5.6.1. How to use it?
Stub Runner Server
Spring Cloud CLI
5.6.2. Endpoints
HTTP
Messaging
5.6.3. Example
5.6.4. Stub Runner Boot with Service Discovery
5.7. Stubs Per Consumer
5.8. Common
5.8.1. Common Properties for JUnit and Spring
5.8.2. Stub Runner Stubs IDs
6. Stub Runner for Messaging
6.1. Stub triggering
6.1.1. Trigger by Label
6.1.2. Trigger by Group and Artifact Ids
6.1.3. Trigger by Artifact Ids
6.1.4. Trigger All Messages
6.2. Stub Runner Camel
6.2.1. Adding the Runner to the Project
6.2.2. Disabling the functionality
Scenario 1 (no input message)
Scenario 2 (output triggered by input)
Scenario 3 (input with no output)
6.3. Stub Runner Integration
6.3.1. Adding the Runner to the Project
6.3.2. Disabling the functionality
Scenario 1 (no input message)
Scenario 2 (output triggered by input)
Scenario 3 (input with no output)
6.4. Stub Runner Stream
6.4.1. Adding the Runner to the Project
6.4.2. Disabling the functionality
Scenario 1 (no input message)
Scenario 2 (output triggered by input)
Scenario 3 (input with no output)
6.5. Stub Runner Spring AMQP
6.5.1. Adding the Runner to the Project
Triggering the message
Spring AMQP Test Configuration
7. Contract DSL
7.1. Limitations
7.2. Common Top-Level elements
7.2.1. Description
7.2.2. Name
7.2.3. Ignoring Contracts
7.2.4. Passing Values from Files
7.2.5. HTTP Top-Level Elements
7.3. Request
7.4. Response
7.5. Dynamic properties
7.5.1. Dynamic properties inside the body
7.5.2. Regular expressions
7.5.3. Passing Optional Parameters
7.5.4. Executing Custom Methods on the Server Side
7.5.5. Referencing the Request from the Response
7.5.6. Registering Your Own WireMock Extension
7.5.7. Dynamic Properties in the Matchers Sections
7.6. JAX-RS Support
7.7. Async Support
7.8. Working with Context Paths
7.9. Messaging Top-Level Elements
7.9.1. Output Triggered by a Method
7.9.2. Output Triggered by a Message
7.9.3. Consumer/Producer
7.10. Multiple Contracts in One File
8. Customization
8.1. Extending the DSL
8.1.1. Common JAR
8.1.2. Adding the Dependency to the Project
8.1.3. Test the Dependency in the Project’s Dependencies
8.1.4. Test a Dependency in the Plugin’s Dependencies
8.1.5. Referencing classes in DSLs
9. Using the Pluggable Architecture
9.1. Custom Contract Converter
9.1.1. Pact Converter
9.1.2. Pact Contract
9.1.3. Pact for Producers
9.1.4. Pact for Consumers
9.2. Using the Custom Test Generator
9.3. Using the Custom Stub Generator
9.4. Using the Custom Stub Runner
9.5. Using the Custom Stub Downloader
10. Spring Cloud Contract WireMock
10.1. Registering Stubs Automatically
10.2. Using Files to Specify the Stub Bodies
10.3. Alternative: Using JUnit Rules
10.4. Relaxed SSL Validation for Rest Template
10.5. WireMock and Spring MVC Mocks
10.6. Generating Stubs using REST Docs
10.7. Generating Contracts by Using REST Docs
11. Migrations
11.1. 1.0.x → 1.1.x
11.1.1. New structure of generated stubs
11.2. 1.1.x → 1.2.x
11.2.1. Custom HttpServerStub
11.2.2. New packages for generated tests
11.2.3. New Methods in TemplateProcessor
11.2.4. RestAssured 3.0
12. Links
   Next
   

\ No newline at end of file
+   Spring Cloud Contract
Spring Cloud Contract
   Next
Spring Cloud Contract
Table of Contents
1. Spring Cloud Contract
2. Spring Cloud Contract Verifier Introduction
2.1. Why a Contract Verifier?
2.1.1. Testing issues
2.2. Purposes
2.3. How It Works
2.3.1. Defining the contract
2.3.2. Client Side
2.3.3. Server Side
2.4. Step-by-step Guide to Consumer Driven Contracts (CDC)
2.4.1. Technical note
2.4.2. Consumer side (Loan Issuance)
2.4.3. Producer side (Fraud Detection server)
2.4.4. Consumer Side (Loan Issuance) Final Step
2.5. Dependencies
2.6. Additional Links
2.6.1. Spring Cloud Contract video
2.6.2. Readings
2.7. Samples
3. Spring Cloud Contract Verifier Setup
3.1. Gradle Project
3.1.1. Prerequisites
3.1.2. Add Gradle Plugin with Dependencies
3.1.3. Gradle and Rest Assured 2.0
3.1.4. Snapshot Versions for Gradle
3.1.5. Add stubs
3.1.6. Run the Plugin
3.1.7. Default Setup
3.1.8. Configure Plugin
3.1.9. Configuration Options
3.1.10. Single Base Class for All Tests
3.1.11. Different Base Classes for Contracts
3.1.12. Invoking Generated Tests
3.1.13. Spring Cloud Contract Verifier on the Consumer Side
3.2. Maven Project
3.2.1. Add maven plugin
3.2.2. Maven and Rest Assured 2.0
3.2.3. Snapshot versions for Maven
3.2.4. Add stubs
3.2.5. Run plugin
3.2.6. Configure plugin
3.2.7. Configuration Options
3.2.8. Single Base Class for All Tests
3.2.9. Different base classes for contracts
3.2.10. Invoking generated tests
3.2.11. Maven Plugin and STS
3.2.12. Spring Cloud Contract Verifier on the Consumer Side
3.3. Stubs and Transitive Dependencies
3.4. Scenarios
4. Spring Cloud Contract Verifier Messaging
4.1. Integrations
4.2. Manual Integration Testing
4.3. Publisher-Side Test Generation
4.3.1. Scenario 1: No Input Message
4.3.2. Scenario 2: Output Triggered by Input
4.3.3. Scenario 3: No Output Message
4.4. Consumer Stub Generation
5. Spring Cloud Contract Stub Runner
5.1. Snapshot versions
5.2. Publishing Stubs as JARs
5.3. Stub Runner Core
5.3.1. Retrieving stubs
Stub downloading
Classpath scanning
5.3.2. Running stubs
Limitations
Running using main app
HTTP Stubs
Viewing registered mappings
Messaging Stubs
5.4. Stub Runner JUnit Rule
5.4.1. Maven settings
5.4.2. Providing fixed ports
5.4.3. Fluent API
5.4.4. Stub Runner with Spring
5.5. Stub Runner Spring Cloud
5.5.1. Stubbing Service Discovery
Test profiles and service discovery
5.5.2. Additional Configuration
5.6. Stub Runner Boot Application
5.6.1. How to use it?
Stub Runner Server
Spring Cloud CLI
5.6.2. Endpoints
HTTP
Messaging
5.6.3. Example
5.6.4. Stub Runner Boot with Service Discovery
5.7. Stubs Per Consumer
5.8. Common
5.8.1. Common Properties for JUnit and Spring
5.8.2. Stub Runner Stubs IDs
6. Stub Runner for Messaging
6.1. Stub triggering
6.1.1. Trigger by Label
6.1.2. Trigger by Group and Artifact Ids
6.1.3. Trigger by Artifact Ids
6.1.4. Trigger All Messages
6.2. Stub Runner Camel
6.2.1. Adding the Runner to the Project
6.2.2. Disabling the functionality
Scenario 1 (no input message)
Scenario 2 (output triggered by input)
Scenario 3 (input with no output)
6.3. Stub Runner Integration
6.3.1. Adding the Runner to the Project
6.3.2. Disabling the functionality
Scenario 1 (no input message)
Scenario 2 (output triggered by input)
Scenario 3 (input with no output)
6.4. Stub Runner Stream
6.4.1. Adding the Runner to the Project
6.4.2. Disabling the functionality
Scenario 1 (no input message)
Scenario 2 (output triggered by input)
Scenario 3 (input with no output)
6.5. Stub Runner Spring AMQP
6.5.1. Adding the Runner to the Project
Triggering the message
Spring AMQP Test Configuration
7. Contract DSL
7.1. Limitations
7.2. Common Top-Level elements
7.2.1. Description
7.2.2. Name
7.2.3. Ignoring Contracts
7.2.4. Passing Values from Files
7.2.5. HTTP Top-Level Elements
7.3. Request
7.4. Response
7.5. Dynamic properties
7.5.1. Dynamic properties inside the body
7.5.2. Regular expressions
7.5.3. Passing Optional Parameters
7.5.4. Executing Custom Methods on the Server Side
7.5.5. Referencing the Request from the Response
7.5.6. Registering Your Own WireMock Extension
7.5.7. Dynamic Properties in the Matchers Sections
7.6. JAX-RS Support
7.7. Async Support
7.8. Working with Context Paths
7.9. Messaging Top-Level Elements
7.9.1. Output Triggered by a Method
7.9.2. Output Triggered by a Message
7.9.3. Consumer/Producer
7.9.4. Common
7.10. Multiple Contracts in One File
8. Customization
8.1. Extending the DSL
8.1.1. Common JAR
8.1.2. Adding the Dependency to the Project
8.1.3. Test the Dependency in the Project’s Dependencies
8.1.4. Test a Dependency in the Plugin’s Dependencies
8.1.5. Referencing classes in DSLs
9. Using the Pluggable Architecture
9.1. Custom Contract Converter
9.1.1. Pact Converter
9.1.2. Pact Contract
9.1.3. Pact for Producers
9.1.4. Pact for Consumers
9.2. Using the Custom Test Generator
9.3. Using the Custom Stub Generator
9.4. Using the Custom Stub Runner
9.5. Using the Custom Stub Downloader
10. Spring Cloud Contract WireMock
10.1. Registering Stubs Automatically
10.2. Using Files to Specify the Stub Bodies
10.3. Alternative: Using JUnit Rules
10.4. Relaxed SSL Validation for Rest Template
10.5. WireMock and Spring MVC Mocks
10.6. Generating Stubs using REST Docs
10.7. Generating Contracts by Using REST Docs
11. Migrations
11.1. 1.0.x → 1.1.x
11.1.1. New structure of generated stubs
11.2. 1.1.x → 1.2.x
11.2.1. Custom HttpServerStub
11.2.2. New packages for generated tests
11.2.3. New Methods in TemplateProcessor
11.2.4. RestAssured 3.0
12. Links
   Next
   

\ No newline at end of file
diff --git a/single/spring-cloud-contract.html b/single/spring-cloud-contract.html
index e799408472..b6ee36e5cb 100644
--- a/single/spring-cloud-contract.html
+++ b/single/spring-cloud-contract.html
@@ -1,6 +1,6 @@
 
       
-   Spring Cloud Contract
Spring Cloud Contract
Table of Contents
1. Spring Cloud Contract
2. Spring Cloud Contract Verifier Introduction
2.1. Why a Contract Verifier?
2.1.1. Testing issues
2.2. Purposes
2.3. How It Works
2.3.1. Defining the contract
2.3.2. Client Side
2.3.3. Server Side
2.4. Step-by-step Guide to Consumer Driven Contracts (CDC)
2.4.1. Technical note
2.4.2. Consumer side (Loan Issuance)
2.4.3. Producer side (Fraud Detection server)
2.4.4. Consumer Side (Loan Issuance) Final Step
2.5. Dependencies
2.6. Additional Links
2.6.1. Spring Cloud Contract video
2.6.2. Readings
2.7. Samples
3. Spring Cloud Contract Verifier Setup
3.1. Gradle Project
3.1.1. Prerequisites
3.1.2. Add Gradle Plugin with Dependencies
3.1.3. Gradle and Rest Assured 2.0
3.1.4. Snapshot Versions for Gradle
3.1.5. Add stubs
3.1.6. Run the Plugin
3.1.7. Default Setup
3.1.8. Configure Plugin
3.1.9. Configuration Options
3.1.10. Single Base Class for All Tests
3.1.11. Different Base Classes for Contracts
3.1.12. Invoking Generated Tests
3.1.13. Spring Cloud Contract Verifier on the Consumer Side
3.2. Maven Project
3.2.1. Add maven plugin
3.2.2. Maven and Rest Assured 2.0
3.2.3. Snapshot versions for Maven
3.2.4. Add stubs
3.2.5. Run plugin
3.2.6. Configure plugin
3.2.7. Configuration Options
3.2.8. Single Base Class for All Tests
3.2.9. Different base classes for contracts
3.2.10. Invoking generated tests
3.2.11. Maven Plugin and STS
3.2.12. Spring Cloud Contract Verifier on the Consumer Side
3.3. Stubs and Transitive Dependencies
3.4. Scenarios
4. Spring Cloud Contract Verifier Messaging
4.1. Integrations
4.2. Manual Integration Testing
4.3. Publisher-Side Test Generation
4.3.1. Scenario 1: No Input Message
4.3.2. Scenario 2: Output Triggered by Input
4.3.3. Scenario 3: No Output Message
4.4. Consumer Stub Generation
5. Spring Cloud Contract Stub Runner
5.1. Snapshot versions
5.2. Publishing Stubs as JARs
5.3. Stub Runner Core
5.3.1. Retrieving stubs
Stub downloading
Classpath scanning
5.3.2. Running stubs
Limitations
Running using main app
HTTP Stubs
Viewing registered mappings
Messaging Stubs
5.4. Stub Runner JUnit Rule
5.4.1. Maven settings
5.4.2. Providing fixed ports
5.4.3. Fluent API
5.4.4. Stub Runner with Spring
5.5. Stub Runner Spring Cloud
5.5.1. Stubbing Service Discovery
Test profiles and service discovery
5.5.2. Additional Configuration
5.6. Stub Runner Boot Application
5.6.1. How to use it?
Stub Runner Server
Spring Cloud CLI
5.6.2. Endpoints
HTTP
Messaging
5.6.3. Example
5.6.4. Stub Runner Boot with Service Discovery
5.7. Stubs Per Consumer
5.8. Common
5.8.1. Common Properties for JUnit and Spring
5.8.2. Stub Runner Stubs IDs
6. Stub Runner for Messaging
6.1. Stub triggering
6.1.1. Trigger by Label
6.1.2. Trigger by Group and Artifact Ids
6.1.3. Trigger by Artifact Ids
6.1.4. Trigger All Messages
6.2. Stub Runner Camel
6.2.1. Adding the Runner to the Project
6.2.2. Disabling the functionality
Scenario 1 (no input message)
Scenario 2 (output triggered by input)
Scenario 3 (input with no output)
6.3. Stub Runner Integration
6.3.1. Adding the Runner to the Project
6.3.2. Disabling the functionality
Scenario 1 (no input message)
Scenario 2 (output triggered by input)
Scenario 3 (input with no output)
6.4. Stub Runner Stream
6.4.1. Adding the Runner to the Project
6.4.2. Disabling the functionality
Scenario 1 (no input message)
Scenario 2 (output triggered by input)
Scenario 3 (input with no output)
6.5. Stub Runner Spring AMQP
6.5.1. Adding the Runner to the Project
Triggering the message
Spring AMQP Test Configuration
7. Contract DSL
7.1. Limitations
7.2. Common Top-Level elements
7.2.1. Description
7.2.2. Name
7.2.3. Ignoring Contracts
7.2.4. Passing Values from Files
7.2.5. HTTP Top-Level Elements
7.3. Request
7.4. Response
7.5. Dynamic properties
7.5.1. Dynamic properties inside the body
7.5.2. Regular expressions
7.5.3. Passing Optional Parameters
7.5.4. Executing Custom Methods on the Server Side
7.5.5. Referencing the Request from the Response
7.5.6. Registering Your Own WireMock Extension
7.5.7. Dynamic Properties in the Matchers Sections
7.6. JAX-RS Support
7.7. Async Support
7.8. Working with Context Paths
7.9. Messaging Top-Level Elements
7.9.1. Output Triggered by a Method
7.9.2. Output Triggered by a Message
7.9.3. Consumer/Producer
7.10. Multiple Contracts in One File
8. Customization
8.1. Extending the DSL
8.1.1. Common JAR
8.1.2. Adding the Dependency to the Project
8.1.3. Test the Dependency in the Project’s Dependencies
8.1.4. Test a Dependency in the Plugin’s Dependencies
8.1.5. Referencing classes in DSLs
9. Using the Pluggable Architecture
9.1. Custom Contract Converter
9.1.1. Pact Converter
9.1.2. Pact Contract
9.1.3. Pact for Producers
9.1.4. Pact for Consumers
9.2. Using the Custom Test Generator
9.3. Using the Custom Stub Generator
9.4. Using the Custom Stub Runner
9.5. Using the Custom Stub Downloader
10. Spring Cloud Contract WireMock
10.1. Registering Stubs Automatically
10.2. Using Files to Specify the Stub Bodies
10.3. Alternative: Using JUnit Rules
10.4. Relaxed SSL Validation for Rest Template
10.5. WireMock and Spring MVC Mocks
10.6. Generating Stubs using REST Docs
10.7. Generating Contracts by Using REST Docs
11. Migrations
11.1. 1.0.x → 1.1.x
11.1.1. New structure of generated stubs
11.2. 1.1.x → 1.2.x
11.2.1. Custom HttpServerStub
11.2.2. New packages for generated tests
11.2.3. New Methods in TemplateProcessor
11.2.4. RestAssured 3.0
12. Links
Documentation Authors: Adam Dudczak, Mathias Düsterhöft, Marcin Grzejszczak, Dennis Kieselhorst, Jakub Kubryński, Karol Lassak,
+   Spring Cloud Contract
Spring Cloud Contract
Table of Contents
1. Spring Cloud Contract
2. Spring Cloud Contract Verifier Introduction
2.1. Why a Contract Verifier?
2.1.1. Testing issues
2.2. Purposes
2.3. How It Works
2.3.1. Defining the contract
2.3.2. Client Side
2.3.3. Server Side
2.4. Step-by-step Guide to Consumer Driven Contracts (CDC)
2.4.1. Technical note
2.4.2. Consumer side (Loan Issuance)
2.4.3. Producer side (Fraud Detection server)
2.4.4. Consumer Side (Loan Issuance) Final Step
2.5. Dependencies
2.6. Additional Links
2.6.1. Spring Cloud Contract video
2.6.2. Readings
2.7. Samples
3. Spring Cloud Contract Verifier Setup
3.1. Gradle Project
3.1.1. Prerequisites
3.1.2. Add Gradle Plugin with Dependencies
3.1.3. Gradle and Rest Assured 2.0
3.1.4. Snapshot Versions for Gradle
3.1.5. Add stubs
3.1.6. Run the Plugin
3.1.7. Default Setup
3.1.8. Configure Plugin
3.1.9. Configuration Options
3.1.10. Single Base Class for All Tests
3.1.11. Different Base Classes for Contracts
3.1.12. Invoking Generated Tests
3.1.13. Spring Cloud Contract Verifier on the Consumer Side
3.2. Maven Project
3.2.1. Add maven plugin
3.2.2. Maven and Rest Assured 2.0
3.2.3. Snapshot versions for Maven
3.2.4. Add stubs
3.2.5. Run plugin
3.2.6. Configure plugin
3.2.7. Configuration Options
3.2.8. Single Base Class for All Tests
3.2.9. Different base classes for contracts
3.2.10. Invoking generated tests
3.2.11. Maven Plugin and STS
3.2.12. Spring Cloud Contract Verifier on the Consumer Side
3.3. Stubs and Transitive Dependencies
3.4. Scenarios
4. Spring Cloud Contract Verifier Messaging
4.1. Integrations
4.2. Manual Integration Testing
4.3. Publisher-Side Test Generation
4.3.1. Scenario 1: No Input Message
4.3.2. Scenario 2: Output Triggered by Input
4.3.3. Scenario 3: No Output Message
4.4. Consumer Stub Generation
5. Spring Cloud Contract Stub Runner
5.1. Snapshot versions
5.2. Publishing Stubs as JARs
5.3. Stub Runner Core
5.3.1. Retrieving stubs
Stub downloading
Classpath scanning
5.3.2. Running stubs
Limitations
Running using main app
HTTP Stubs
Viewing registered mappings
Messaging Stubs
5.4. Stub Runner JUnit Rule
5.4.1. Maven settings
5.4.2. Providing fixed ports
5.4.3. Fluent API
5.4.4. Stub Runner with Spring
5.5. Stub Runner Spring Cloud
5.5.1. Stubbing Service Discovery
Test profiles and service discovery
5.5.2. Additional Configuration
5.6. Stub Runner Boot Application
5.6.1. How to use it?
Stub Runner Server
Spring Cloud CLI
5.6.2. Endpoints
HTTP
Messaging
5.6.3. Example
5.6.4. Stub Runner Boot with Service Discovery
5.7. Stubs Per Consumer
5.8. Common
5.8.1. Common Properties for JUnit and Spring
5.8.2. Stub Runner Stubs IDs
6. Stub Runner for Messaging
6.1. Stub triggering
6.1.1. Trigger by Label
6.1.2. Trigger by Group and Artifact Ids
6.1.3. Trigger by Artifact Ids
6.1.4. Trigger All Messages
6.2. Stub Runner Camel
6.2.1. Adding the Runner to the Project
6.2.2. Disabling the functionality
Scenario 1 (no input message)
Scenario 2 (output triggered by input)
Scenario 3 (input with no output)
6.3. Stub Runner Integration
6.3.1. Adding the Runner to the Project
6.3.2. Disabling the functionality
Scenario 1 (no input message)
Scenario 2 (output triggered by input)
Scenario 3 (input with no output)
6.4. Stub Runner Stream
6.4.1. Adding the Runner to the Project
6.4.2. Disabling the functionality
Scenario 1 (no input message)
Scenario 2 (output triggered by input)
Scenario 3 (input with no output)
6.5. Stub Runner Spring AMQP
6.5.1. Adding the Runner to the Project
Triggering the message
Spring AMQP Test Configuration
7. Contract DSL
7.1. Limitations
7.2. Common Top-Level elements
7.2.1. Description
7.2.2. Name
7.2.3. Ignoring Contracts
7.2.4. Passing Values from Files
7.2.5. HTTP Top-Level Elements
7.3. Request
7.4. Response
7.5. Dynamic properties
7.5.1. Dynamic properties inside the body
7.5.2. Regular expressions
7.5.3. Passing Optional Parameters
7.5.4. Executing Custom Methods on the Server Side
7.5.5. Referencing the Request from the Response
7.5.6. Registering Your Own WireMock Extension
7.5.7. Dynamic Properties in the Matchers Sections
7.6. JAX-RS Support
7.7. Async Support
7.8. Working with Context Paths
7.9. Messaging Top-Level Elements
7.9.1. Output Triggered by a Method
7.9.2. Output Triggered by a Message
7.9.3. Consumer/Producer
7.9.4. Common
7.10. Multiple Contracts in One File
8. Customization
8.1. Extending the DSL
8.1.1. Common JAR
8.1.2. Adding the Dependency to the Project
8.1.3. Test the Dependency in the Project’s Dependencies
8.1.4. Test a Dependency in the Plugin’s Dependencies
8.1.5. Referencing classes in DSLs
9. Using the Pluggable Architecture
9.1. Custom Contract Converter
9.1.1. Pact Converter
9.1.2. Pact Contract
9.1.3. Pact for Producers
9.1.4. Pact for Consumers
9.2. Using the Custom Test Generator
9.3. Using the Custom Stub Generator
9.4. Using the Custom Stub Runner
9.5. Using the Custom Stub Downloader
10. Spring Cloud Contract WireMock
10.1. Registering Stubs Automatically
10.2. Using Files to Specify the Stub Bodies
10.3. Alternative: Using JUnit Rules
10.4. Relaxed SSL Validation for Rest Template
10.5. WireMock and Spring MVC Mocks
10.6. Generating Stubs using REST Docs
10.7. Generating Contracts by Using REST Docs
11. Migrations
11.1. 1.0.x → 1.1.x
11.1.1. New structure of generated stubs
11.2. 1.1.x → 1.2.x
11.2.1. Custom HttpServerStub
11.2.2. New packages for generated tests
11.2.3. New Methods in TemplateProcessor
11.2.4. RestAssured 3.0
12. Links
Documentation Authors: Adam Dudczak, Mathias Düsterhöft, Marcin Grzejszczak, Dennis Kieselhorst, Jakub Kubryński, Karol Lassak,
 Olga Maciaszek-Sharma, Mariusz Smykuła, Dave Syer, Jay Bryant
1.2.0.BUILD-SNAPSHOT
1. Spring Cloud Contract
You need confidence when pushing new features to a new application or service in a
 distributed system. This project provides support for Consumer Driven Contracts and
 service schemas in Spring applications (for both HTTP and message-based interactions),
@@ -3333,7 +3333,7 @@ socket.
Consider the following contract:
or
 }
If you do it this way:
  • All of your requests in the autogenerated tests are sent to the real endpoint with your
 context path included (for example, /my-context-path/url).
  • Your contracts reflect that you have a context path. Your generated stubs also have
 that information (for example, in the stubs, you have to call /my-context-path/url).
7.9 Messaging Top-Level Elements
The DSL for messaging looks a little bit different than the one that focuses on HTTP. The
-following sections explain the differences:
7.9.1 Output Triggered by a Method
The output message can be triggered by calling a method (such as a Scheduler when a was
+following sections explain the differences:
7.9.1 Output Triggered by a Method
The output message can be triggered by calling a method (such as a Scheduler when a was
 started and a message was sent), as shown in the following example:
def dsl = Contract.make {
 	// Human readable description
 	description 'Some description'
@@ -3409,7 +3409,10 @@ parts):
Contract.make {
 				bookName: 'foo'
 		])
 	}
-}
7.10 Multiple Contracts in One File
You can define multiple contracts in one file. Such a contract might resemble the
+}

7.9.4 Common

In the input {} or outputMessage {} section you can call assertThat with the name +of a method (e.g. assertThatMessageIsOnTheQueue()) that you have defined in the +base class or in a static import. Spring Cloud Pipelines will execute that method +in the genertaed test.

7.10 Multiple Contracts in One File

You can define multiple contracts in one file. Such a contract might resemble the following example:

import org.springframework.cloud.contract.spec.Contract
 
 [
diff --git a/spring-cloud-contract.xml b/spring-cloud-contract.xml
index 35e86cc393..73249ad0d6 100644
--- a/spring-cloud-contract.xml
+++ b/spring-cloud-contract.xml
@@ -5438,6 +5438,9 @@ following sections explain the differences:
 
 
 
+
+
+
 
 

 Output Triggered by a Method
@@ -5532,6 +5535,13 @@ parts):
 	}
 }
 

+

+Common
+In the input {} or outputMessage {} section you can call assertThat with the name
+of a method (e.g. assertThatMessageIsOnTheQueue()) that you have defined in the
+base class or in a static import. Spring Cloud Pipelines will execute that method
+in the genertaed test.
+

 
 

 Multiple Contracts in One File