Squashed 'compatibility-suite/pact-compatibility-suite/' changes from 4db89a19c..bd6b2044c

bd6b2044c feat: Add V4 message scenarios

git-subtree-dir: compatibility-suite/pact-compatibility-suite
git-subtree-split: bd6b2044c205cf10e47bb386e384d9283faae325

Author: rholshausen

features/V4/message_consumer.feature

@@ -0,0 +1,26 @@
+@consumer @message
+Feature: Message consumer
+  Supports V4 async message consumer interactions
+
+  Scenario: Sets the type for the interaction
+    Given a message interaction is being defined for a consumer test
+    When the Pact file for the test is generated
+    Then the first interaction in the Pact file will have a type of "Asynchronous/Messages"
+
+  Scenario: Supports specifying a key for the interaction
+    Given a message interaction is being defined for a consumer test
+    And a key of "123ABC" is specified for the message interaction
+    When the Pact file for the test is generated
+    Then the first interaction in the Pact file will have "key" = '"123ABC"'
+
+  Scenario: Supports specifying the interaction is pending
+    Given a message interaction is being defined for a consumer test
+    And the message interaction is marked as pending
+    When the Pact file for the test is generated
+    Then the first interaction in the Pact file will have "pending" = 'true'
+
+  Scenario: Supports adding comments
+    Given a message interaction is being defined for a consumer test
+    And a comment "this is a comment" is added to the message interaction
+    When the Pact file for the test is generated
+    Then the first interaction in the Pact file will have "comments" = '{"text":["this is a comment"]}'

features/V4/message_provider.feature

@@ -0,0 +1,22 @@
+@provider @message
+Feature: Message provider
+  Supports verifying a async message provider using V4 features
+
+  Scenario: Verifying a pending message interaction
+    Given a provider is started that can generate the "basic" message with "file: basic2.json"
+    And a Pact file for "basic":"file: basic.json" is to be verified, but is marked pending
+    When the verification is run
+    Then the verification will be successful
+    And there will be a pending "Body had differences" error
+
+  Scenario: Verifying a message interaction with comments
+    Given a provider is started that can generate the "basic" message with "file: basic.json"
+    And a Pact file for "basic":"file: basic.json" is to be verified with the following comments:
+      | comment             | type     |
+      | comment one         | text     |
+      | comment two         | text     |
+      | compatibility-suite | testname |
+    When the verification is run
+    Then the comment "comment one" will have been printed to the console
+    And the comment "comment two" will have been printed to the console
+    And the "compatibility-suite" will displayed as the original test name

features/V4/v4.feature

@@ -5,5 +5,5 @@ Feature: General V4 features
     Given an HTTP interaction is being defined for a consumer test
     And a message interaction is being defined for a consumer test
     When the Pact file for the test is generated
-    Then the first interaction in the Pact file will have a type of "Synchronous/HTTP"
-    Then the second interaction in the Pact file will have a type of "Asynchronous/Messages"
+    Then there will be an interaction in the Pact file with a type of "Synchronous/HTTP"
+    And there will be an interaction in the Pact file with a type of "Asynchronous/Messages"