src/test/resources/contract/fraud folder. The fraud folder
+We’re placing the contract under src/test/resources/contracts/fraud folder. The fraud folder
is important cause we’ll reference that folder in the producer’s test base class name.
packageWithBaseClasses property.
That means that 2 last packages will be combined into a name of the base test class. In our case the contracts
-were placed under src/test/resources/contract/fraud. Since we don’t have 2 packages starting from the contracts
+were placed under src/test/resources/contracts/fraud. Since we don’t have 2 packages starting from the contracts
folder we’re picking only one which is fraud. We’re adding the Base suffix and we’re capitalizing fraud.
That gives us the FraudBase test class name.
@@ -1887,7 +1887,7 @@ git merge --no-ff contract-change-pr
work online
Now you can disable the offline work for Spring Cloud Contract Stub Runner ad provide where the repository with your stubs is placed. At this moment the stubs of the server side will be automatically downloaded from Nexus / Artifactory. +
Now you can disable the offline work for Spring Cloud Contract Stub Runner and provide where the repository with your stubs is placed. At this moment the stubs of the server side will be automatically downloaded from Nexus / Artifactory.
You can switch off the value of the workOffline parameter in your annotation. Below you can see an
example of achieving the same by changing the properties.
com.example.base
-
contractsWorkOffline - if the dependencies should be downloaded or local Maven only should be reused
+-
+
cacheDownloadedContracts - if you want to reuse download JARs that contain contract definitions.
+We cache only non-snapshot, explicitly provided versions (e.g. + or 1.0.0.BUILD-SNAPSHOT won’t get cached).
+By default this feature is turned on.
+
For complete information take a look at Plugin Documentation
-