async() method. Example:
Spring Cloud Contract supports context paths.
+|
+ Important
+ |
++The only thing that changes in order to fully support context paths is the switch +on the PRODUCER side. The autogenerated tests need to be using the EXPLICIT mode. + | +
The consumer side remains untouched, in order for the generated test to pass you have to switch the EXPLICIT mode.
+<plugin>
+ <groupId>org.springframework.cloud</groupId>
+ <artifactId>spring-cloud-contract-maven-plugin</artifactId>
+ <version>${spring-cloud-contract.version}</version>
+ <extensions>true</extensions>
+ <configuration>
+ <testMode>EXPLICIT</testMode>
+ </configuration>
+</plugin>contracts {
+ testMode = 'EXPLICIT'
+}That way you’ll generate a test that DOES NOT use MockMvc. It means that you’re generating +real requests and you need to setup your generated test’s base class to work on a real socket.
+Let’s imagine the following contract:
+org.springframework.cloud.contract.spec.Contract.make {
+ request {
+ method 'GET'
+ url '/my-context-path/url'
+ }
+ response {
+ status 200
+ }
+}Here is an example of how to set up a base class and Rest Assured for everything to work correctly.
+import com.jayway.restassured.RestAssured;
+import org.junit.Before;
+import org.springframework.boot.context.embedded.LocalServerPort;
+import org.springframework.boot.test.context.SpringBootTest;
+
+@SpringBootTest(classes = ContextPathTestingBaseClass.class, webEnvironment = SpringBootTest.WebEnvironment.RANDOM_PORT)
+class ContextPathTestingBaseClass {
+
+ @LocalServerPort int port;
+
+ @Before
+ public void setup() {
+ RestAssured.baseURI = "http://localhost";
+ RestAssured.port = this.port;
+ }
+}That way all:
+all your requests in the autogenerated tests will be sent to the real endpoint with your context path included (e.g. /my-context-path/url)
your contracts reflect that you have a context path, thus your generated stubs will also
+have that information (e.g. in the stubs you’ll see that you have too call /my-context-path/url)
The DSL for messaging looks a little bit different than the one that focuses on HTTP.