JVM version of Pact. Enables consumer driven contract testing, providing a mock service and DSL for the consumer project, and interaction playback and verification for the service provider project.
Every next Gradle run it appends the test data to pacts files thus whenever you run the pact publish task after it might cause an unexpected pact data publishing.
The expected behaviour would be that the pact files are regenerated from scratch on every tests run hence the pacts would be consistent with the state of tests (pact DSL).
It's very much close to another issue I have opened recently about the report
When I wrote this I realized that's on the Gradle side probably and we should have a custom task to clean before or is it possible to handle it in JVM runtime?
Problem:
Every next Gradle run it appends the test data to pacts files thus whenever you run the pact publish task after it might cause an unexpected pact data publishing.
The expected behaviour would be that the pact files are regenerated from scratch on every tests run hence the pacts would be consistent with the state of tests (pact DSL).
It's very much close to another issue I have opened recently about the report
When I wrote this I realized that's on the Gradle side probably and we should have a custom task to clean before or is it possible to handle it in JVM runtime?
I can create an example if needed.