Kai Moritz [Sun, 22 May 2022 07:19:09 +0000 (09:19 +0200)]
The contract-test uses a random port on the provider
* This is crucial in most cases, if one planes to execute the test in
a build pipline, because it is very likely, that several tests run in
parallel in that scenario
Kai Moritz [Sat, 21 May 2022 19:19:47 +0000 (21:19 +0200)]
Defined all contracts in a single pact, like in the original example
* Looking back, I have to adhere, that this move is missleading.
* For a newbie (like me) this suggests, that all commands will be
executed in order on the provider, so that the expected state will
be created automatically - but that is not true!
Kai Moritz [Sat, 21 May 2022 10:47:16 +0000 (12:47 +0200)]
Added a Spring-based consumer
* Goal: re-stage the contract with Spring for educational purposes
* Generates a totally different contract for now...
* Is copied from the code-example for the PactDslJsonBody DSL
* See: https://docs.pact.io/implementation_guides/jvm/consumer#building-json-bodies-with-pactdsljsonbody-dsl[example-code]
* Added Maven-Builddirectory to .gitignore
* Added the generated JSON for comparison