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.xml for this component when using Camel 2.8 or older:
<!-- use the same version as your Camel core version -->
From Camel 2.9 onwards the Test
component is provided directly in the camel-core.