Show Table of Contents
Chapter 175. Test
The test component extends the Mock component to support pulling messages from another endpoint on startup to set the expected message bodies on the underlying Mock endpoint. That is, you use the test endpoint in a route and messages arriving on it will be implicitly compared to some expected messages extracted from some other location.
So you can use, for example, an expected set of message bodies as files. This will then set up a properly configured Mock endpoint, which is only valid if the received messages match the number of expected messages and their message payloads are equal.
Maven users will need to add the following dependency to their
pom.xmlfor this component when using Camel 2.8 or older:
<dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-spring</artifactId> <version>2.17.0.redhat-630xxx</version> <!-- use the same version as your Camel core version --> </dependency>
From Camel 2.9 onwards the Test component is provided directly in the camel-core.
Where expectedMessagesEndpointUri refers to some other Component URI that the expected message bodies are pulled from before starting the test.
||Camel 2.12: The timeout to use when polling for message bodies from the URI.|
||Camel 2.17: Whether the expected messages should arrive in the same order or can be in any order.|
Camel 2.17: If enabled, the messages loaded from the test endpoint will be split using
||Camel 2.17: The split delimiter to use when split is enabled. By default the delimiter is new line based. The delimiter can be a regular expression.|
For example, you could write a test case as follows:
If your test then invokes the MockEndpoint.assertIsSatisfied(camelContext) method, your test case will perform the necessary assertions.
To see how you can set other expectations on the test endpoint, see the Mock component.