* Start working on generating stub requests from Xml.
* Start implementing matching by xpath.
* Handle xml request body matchers.
* Merge branch 'master' into add-xml-support
* Implement analysing xmls and converting nodes to matchers.
* Handle attributes in xml analysis and generate stubs with xml body matchers.
* Make XmlToXPathsConverter statically compiled.
* Start extracting json test generation logic out of the MethodBodyBuilder.
* Fix extracted JsonBodyVerificationBuilder. Fix processing attributes
from xml while generating stubs. Fix and adjust tests to recent changes.
* Merge branch 'master' into add-xml-support
# Conflicts:
# spring-cloud-contract-verifier/src/main/groovy/org/springframework/cloud/contract/verifier/builder/MethodBodyBuilder.groovy
# spring-cloud-contract-verifier/src/main/groovy/org/springframework/cloud/contract/verifier/converter/ContractsToYaml.groovy
# spring-cloud-contract-verifier/src/main/groovy/org/springframework/cloud/contract/verifier/dsl/wiremock/WireMockRequestStubStrategy.groovy
# spring-cloud-contract-verifier/src/main/groovy/org/springframework/cloud/contract/verifier/util/JsonToJsonPathsConverter.groovy
# spring-cloud-contract-verifier/src/test/groovy/org/springframework/cloud/contract/verifier/converter/YamlContractConverterSpec.groovy
* Implement test generation for XML body matchers. Start implementing handling XML lists in assertions.
* Fix generating list element assertions and regex body matcher assertions.
Move XML-assert lib content to project sources. Add tests.
* Fix recognising XML content from String body. Minor refactoring.
* Adjust yaml contracts to new xml handling.
* Add tests for handling XML with yaml contracts. Handle incorrect request
matchers processing.
* Minor refactoring.
* Add docs.
* Fix docs.
* Fixes after code review.
* Switch to apache commons logger in `XmlAsserter`.
without this change it's hard to add HTTPs support for the stubs ran by stub runner. It's close to impossible to alter the default configuration of HTTP server stubs at all (e.g. lower the logging level of WireMock stubs etc.)
with this change we allow to pass a class as a property to stub runner either via annotation, JUnit rule / extension or just system properties. That way the configurer will be applied at runtime for WireMock stubs (implementors of custom HTTP server stubs will need to perform some additional work to allow this)
fixes gh-742
without this change you always have to pass the concrete version for git based storage
with this change we support passing of a latests version
fixes gh-745
without this change if one does $(regex("[0-9]")) we have no knowledge of whether the result should be text or a number. What we do ATM is we always generate a String
with this change once can pass the type of regular expression and we will generate the concrete value of that given type
fixes gh-768
without this change, if you're using some external libraries and you reference them in your DSL, those libraries need to also be used on the consumer side.
with this change, you can set the contractsToYaml property of the plugin, that will convert the contract definitions into YAML, and then generate tests and stubs. We will store the original contract definitions under the originals folder.
fixes#744
without this change we always include `spring-boot-starter-web` to Stub Runner. With this change the dependency is optional. Thanks to this reactive applications will be able to work fine with contract on the classpath.
without this change we always run Stub Runner test execution listener, even if the test class is not annotated. With this change we run the listener only, if the test class was annotated with `@AutoConfigureStubRunner`.
Also we add information about the `java.net.SocketException: Unexpected end of file from server` exception to the docs and how to override that issue.
Fixes gh-798, gh-809, gh-799
* fix stub runner application when is in real stream mode
* fix stub runner application when is in real stream mode. Adding @ConditionalOnClass(TestSupportBinderAutoConfiguration.class)
Allow an option to dump contracts as files for the given ContractConverter. In other words, if you have contracts written in e,g, groovy and yml, by providing a FQN of org.springframework.cloud.contract.verifier.converter.YamlContractConverter, you will be able to dump all files in a folder in a yml format.
fixes gh-793
