This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/main by this push:
     new 0b5468c  Polish and cleanup documentation
0b5468c is described below

commit 0b5468c9561e6c016096182eb94931174dcefcf1
Author: Claus Ibsen <claus.ib...@gmail.com>
AuthorDate: Mon Aug 23 14:40:12 2021 +0200

    Polish and cleanup documentation
---
 .../camel/catalog/docs/dataset-test-component.adoc      |  3 ++-
 .../src/main/docs/dataset-test-component.adoc           |  3 ++-
 .../modules/ROOT/pages/dataset-test-component.adoc      |  3 ++-
 docs/user-manual/modules/ROOT/pages/testing.adoc        | 17 +++++++----------
 4 files changed, 13 insertions(+), 13 deletions(-)

diff --git 
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/dataset-test-component.adoc
 
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/dataset-test-component.adoc
index 19ef3b7..c9d7c30 100644
--- 
a/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/dataset-test-component.adoc
+++ 
b/catalog/camel-catalog/src/generated/resources/org/apache/camel/catalog/docs/dataset-test-component.adoc
@@ -25,7 +25,8 @@ together with the powerful Bean Integration.
 The *dataset-test* component extends the xref:mock-component.adoc[Mock] 
component to
 support pulling messages from another endpoint on startup to set the
 expected message bodies on the underlying xref:mock-component.adoc[Mock] 
endpoint.
-That is, you use the test endpoint in a route and messages arriving on
+
+That is, you use the dataset test endpoint in a route and messages arriving at
 it will be implicitly compared to some expected messages extracted from
 some other location.
 
diff --git a/components/camel-dataset/src/main/docs/dataset-test-component.adoc 
b/components/camel-dataset/src/main/docs/dataset-test-component.adoc
index 19ef3b7..c9d7c30 100644
--- a/components/camel-dataset/src/main/docs/dataset-test-component.adoc
+++ b/components/camel-dataset/src/main/docs/dataset-test-component.adoc
@@ -25,7 +25,8 @@ together with the powerful Bean Integration.
 The *dataset-test* component extends the xref:mock-component.adoc[Mock] 
component to
 support pulling messages from another endpoint on startup to set the
 expected message bodies on the underlying xref:mock-component.adoc[Mock] 
endpoint.
-That is, you use the test endpoint in a route and messages arriving on
+
+That is, you use the dataset test endpoint in a route and messages arriving at
 it will be implicitly compared to some expected messages extracted from
 some other location.
 
diff --git a/docs/components/modules/ROOT/pages/dataset-test-component.adoc 
b/docs/components/modules/ROOT/pages/dataset-test-component.adoc
index dd117f2..e577fb3 100644
--- a/docs/components/modules/ROOT/pages/dataset-test-component.adoc
+++ b/docs/components/modules/ROOT/pages/dataset-test-component.adoc
@@ -27,7 +27,8 @@ together with the powerful Bean Integration.
 The *dataset-test* component extends the xref:mock-component.adoc[Mock] 
component to
 support pulling messages from another endpoint on startup to set the
 expected message bodies on the underlying xref:mock-component.adoc[Mock] 
endpoint.
-That is, you use the test endpoint in a route and messages arriving on
+
+That is, you use the dataset test endpoint in a route and messages arriving at
 it will be implicitly compared to some expected messages extracted from
 some other location.
 
diff --git a/docs/user-manual/modules/ROOT/pages/testing.adoc 
b/docs/user-manual/modules/ROOT/pages/testing.adoc
index 369971a..5ef7f24 100644
--- a/docs/user-manual/modules/ROOT/pages/testing.adoc
+++ b/docs/user-manual/modules/ROOT/pages/testing.adoc
@@ -56,16 +56,15 @@ Camel provides a number of xref:endpoint.adoc[endpoints] 
which can make testing
 |=======================================================================
 |Name |Description
 |xref:components::mock-component.adoc[Mock] |For testing routes and mediation 
rules using
-mocks and allowing assertions to be added to an endpoint
-
-|xref:components:others:test.adoc[Test] |Creates a 
xref:components::mock-component.adoc[Mock] endpoint which
-expects to receive all the message bodies that could be polled from the
-given underlying endpoint
+mocks and allowing assertions to be added to an endpoint.
 
 |xref:components::dataset-component.adoc[DataSet] |For load & soak testing 
this endpoint
 provides a way to create huge numbers of messages for sending to
-Components and asserting that they are consumed
-correctly
+components and asserting that they are consumed correctly.
+
+|xref:components::dataset-test-component.adoc[DataSet Test] |Used for 
automatic load
+a set of expected message from another endpoint which is then compared to the 
messages
+that arrives at this endpoint.
 
 |=======================================================================
 
@@ -110,7 +109,7 @@ completed 5 messages. You can build complex expressions to 
match your
 criteria when to be notified.
 
 |AdviceWith |Allows you to _advice_ (enhance)
-an existing route using a `RouteBuilder` style.
+an existing route using a xref:route-builder.adoc[RouteBuilder] style.
 For example, you can send (or send and skip) message to a 
xref:components::mock-component.adoc[Mock]
 endpoint for validating the message send by Camel is as expected.
 |=======================================================================
@@ -123,7 +122,5 @@ There are a number of third party testing libraries that 
Camel users have found
 |=======================================================================
 |Name |Description
 | https://citrusframework.org/[Citrus Integration Framework] | Framework for 
automated integration tests supporting a wide range of message protocols and 
data formats
-
 | https://citrusframework.org/yaks/[Citrus Yaks] | YAKS is a framework to 
enable Cloud Native BDD testing on Kubernetes
-
 |=======================================================================

Reply via email to