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.
Steps to reproduce:
I have a service that can act as both the provider as well as the consumer, hence i have added the specifications to the same maven plugin configuration. the problem is, the pact authentication specification has to be specified twice, else i run into a null pointer.
The specifications should be good to be provided only once . In a microservices environment, there are many situations where the same service can act as both consumer and provider.
The Maven plugin has been updated (as of version 4.0.6), where the Pact Broker values will default to the top level ones, so they don't have to be repeated.
Versions used: pact-jvm-consumer-junit_2.11.version = 3.5.20 pact-jvm-provider-junit_2.12.version = 3.5.20 pact-jvm-provider-maven_2.11.version= 3.5.20
Steps to reproduce: I have a service that can act as both the provider as well as the consumer, hence i have added the specifications to the same maven plugin configuration. the problem is, the pact authentication specification has to be specified twice, else i run into a null pointer.
Expected Behaviour:
The specifications should be good to be provided only once . In a microservices environment, there are many situations where the same service can act as both consumer and provider.