...
Include Page |
---|
| Testing Summary Include |
---|
| Testing Summary Include |
---|
|
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.
...
Maven users will need to add the following dependency to their pom.xml
for this component when using Camel 2.8 or older:
Code Block |
---|
|
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-spring</artifactId>
<version>x.x.x</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
.
URI format
Code Block |
---|
test:expectedMessagesEndpointUri
|
Where Where expectedMessagesEndpointUri
refers to some other Component URI that the expected message bodies are pulled from before starting the test.
...
Div |
---|
class | confluenceTableSmall |
---|
|
Name | Default Value | Description | timeout
| 2000 |
---|
Camel 2.12: The timeout to use when polling for message bodies from the URI. | anyOrder | false | Camel 2.17: Whether the expected messages should arrive in the same order, or | can be in any order. | delimiter | \n|\r | Camel 2.17: The delimiter to use when split=true . The delimiter can be a regular expression. | split | false | Camel 2.17: | If enabled the If true the messages loaded from the test endpoint will be split using | \n\r delimiters (new lines) the delimiter so each line is an expected message. For example to use | a a file endpoint to load a file where each line is an expected message. | delimiter | \n|\r timeout
| 2000
| Camel 2. | 1712: The | split delimiter timeout to use when | split is enabled. By default the delimiter is new line based. The delimiter can be a regular expression.polling for message bodies from the URI. |
|
Example
For example, you could write a test case as follows:
Code Block |
---|
|
from("seda:someEndpoint").
.to("test:file://data/expectedOutput?noop=true");
|
...