pact-jvm-consumer-groovy-v3_2.10 · pact-jvm-consumer-groovy-v3 =========================== Groovy DSL for Pact JVM implementing V3 specification changes. ##Dependency The library is available on maven central using: * group-id = `au.com.dius` * artifact-id = `pact-jvm-consumer-groovy-v3_2.11` * version-id = `2.2.x` or `3.0.x` ##Usage Add the `pact-jvm-consumer-groovy-v3` library to your test class path. This provides a `PactMessageBuilder` class for you to use to define your pacts. If you are using gradle for your build, add it to your `build.gradle`: dependencies { testCompile 'au.com.dius:pact-jvm-consumer-groovy-v3_2.11:2.2.12' } ## Consumer test for a message consumer The `PactMessageBuilder` class provides a DSL for defining your message expectations. It works in much the same way as the `PactBuilder` class for Request-Response interactions. ### Step 1 - define the message expectations Create a test that uses the `PactMessageBuilder` to define a message expectation, and then call `run`. This will invoke the given closure with a message for each one defined in the pact. ```groovy def eventStream = new PactMessageBuilder().call { serviceConsumer 'messageConsumer' hasPactWith 'messageProducer' given 'order with id 10000004 exists' expectsToReceive 'an order confirmation message' withMetaData(type: 'OrderConfirmed') // Can define any key-value pairs here withContent(contentType: 'application/json') { type 'OrderConfirmed' audit { userCode 'messageService' } origin 'message-service' referenceId '10000004-2' timeSent: '2015-07-22T10:14:28+00:00' value { orderId '10000004' value '10.000000' fee '10.00' gst '15.00' } } } ``` ### Step 2 - call your message handler with the generated messages This example tests a message handler that gets messages from a Kafka topic. In this case the Pact message is wrapped as a Kafka `MessageAndMetadata`. ```groovy eventStream.run { Message message -> messageHandler.handleMessage(new MessageAndMetadata('topic', 1, new kafka.message.Message(message.contentsAsBytes()), 0, null, valueDecoder)) } ``` ### Step 3 - validate that the message was handled correctly ```groovy def order = orderRepository.getOrder('10000004') assert order.status == 'confirmed' assert order.value == 10.0 ``` ### Step 4 - Publish the pact file If the test was successful, a pact file would have been produced with the message from step 1.

Table Of Contents

• Latest Version
• All Versions
• View Java Class Source Code in JAR file

Latest Version

Download au.com.dius : pact-jvm-consumer-groovy-v3_2.10 JAR file - Latest Versions:

• Latest Stable: 2.2.15.jar

All Versions

Download au.com.dius : pact-jvm-consumer-groovy-v3_2.10 JAR file - All Versions:

Version		Vulnerabilities	Size	Updated
2.2.x	pact-jvm-consumer-groovy-v3_2.10-2.2.15.jar		9.78 KB	Sep 17, 2015
	pact-jvm-consumer-groovy-v3_2.10-2.2.14.jar		9.55 KB	Sep 07, 2015
	pact-jvm-consumer-groovy-v3_2.10-2.2.13.jar		9.55 KB	Aug 29, 2015
	pact-jvm-consumer-groovy-v3_2.10-2.2.12.jar		9.55 KB	Aug 09, 2015
	pact-jvm-consumer-groovy-v3_2.10-2.2.11.jar		9.50 KB	Aug 02, 2015

View Java Class Source Code in JAR file

1. Download JD-GUI to open JAR file and explore Java source code file (.class .java)
2. Click menu "File → Open File..." or just drag-and-drop the JAR file in the JD-GUI window pact-jvm-consumer-groovy-v3_2.10-2.2.15.jar file.
   Once you open a JAR file, all the java classes in the JAR file will be displayed.

au.com.dius.pact.consumer.groovy.messaging

├─ au.com.dius.pact.consumer.groovy.messaging.MessagePactFailedException.class - [JAR]

├─ au.com.dius.pact.consumer.groovy.messaging.PactMessageBuilder.class - [JAR]