diff --git a/docs/src/main/asciidoc/verifier/messaging.adoc b/docs/src/main/asciidoc/verifier/messaging.adoc
index 74f2dcdbcc..bc6a1f87bc 100644
--- a/docs/src/main/asciidoc/verifier/messaging.adoc
+++ b/docs/src/main/asciidoc/verifier/messaging.adoc
@@ -18,6 +18,26 @@ to the classpath then automatically all the messaging configuration will be set
IMPORTANT: Remember to put `@AutoConfigureMessageVerifier` on the base class of your
generated tests. Otherwise messaging part of Spring Cloud Contract Verifier will not work.
+IMPORTANT: If you want to use Spring Cloud Stream remember to add a
+`org.springframework.cloud:spring-cloud-stream-test-support` dependency.
+
+[source,xml,indent=0,subs="verbatim,attributes",role="primary"]
+.Maven
+----
+
+ org.springframework.cloud
+ spring-cloud-stream-test-support
+ test
+
+----
+
+[source,groovy,indent=0,subs="verbatim,attributes",role="secondary"]
+.Gradle
+----
+testCompile "org.springframework.cloud:spring-cloud-stream-test-support"
+----
+
+
==== Manual Integration Testing
The main interface used by the tests is the `org.springframework.cloud.contract.verifier.messaging.MessageVerifier`.
@@ -56,6 +76,12 @@ inside the application (e.g. scheduler)
- Scenario 2: the input message triggers an output message
- Scenario 3: the input message is consumed and there is no output message
+IMPORTANT: The destination passed to `messageFrom` or `sentTo` can have different meanings for different
+ messaging implementations. For *Stream* and *Integration* it's first resolved as a `destination` of a channel, and then if
+ there is no such `destination` it's resolved as a channel name. For *Camel* that's a certain component (e.x. `jms`).
+
+Example for Camel:
+
===== Scenario 1 (no input message)
For the given contract:
diff --git a/tests/spring-cloud-contract-stub-runner-stream/README.adoc b/tests/spring-cloud-contract-stub-runner-stream/README.adoc
index a2b45d60fb..138aec9262 100644
--- a/tests/spring-cloud-contract-stub-runner-stream/README.adoc
+++ b/tests/spring-cloud-contract-stub-runner-stream/README.adoc
@@ -8,6 +8,25 @@ WARNING: In Stub Runner's integration with Stream the `messageFrom` or `sentTo`
first as a `destination` of a channel, and then if there is no such `destination` it's resolved as a
channel name.
+IMPORTANT: If you want to use Spring Cloud Stream remember to add a
+`org.springframework.cloud:spring-cloud-stream-test-support` dependency.
+
+[source,xml,indent=0,subs="verbatim,attributes",role="primary"]
+.Maven
+----
+
+ org.springframework.cloud
+ spring-cloud-stream-test-support
+ test
+
+----
+
+[source,groovy,indent=0,subs="verbatim,attributes",role="secondary"]
+.Gradle
+----
+testCompile "org.springframework.cloud:spring-cloud-stream-test-support"
+----
+
==== Adding it to the project
It's enough to have both Spring Cloud Stream and Spring Cloud Contract Stub Runner on classpath.