34.9. 模拟现有端点
Camel 现在允许您自动模拟 Camel 路由中的现有端点。
它的工作原理
端点仍在操作中。不同的情况是,Mock 端点被先注入并接收消息,然后将消息委派给目标端点。您可以将它视为一种拦截器和委派或端点监听程序。
假设您有以下给定路由:
Route(路由)
@Override
protected RouteBuilder createRouteBuilder() throws Exception {
return new RouteBuilder() {
@Override
public void configure() throws Exception {
from("direct:start").routeId("start")
.to("direct:foo").to("log:foo").to("mock:result");
from("direct:foo").routeId("foo")
.transform(constant("Bye World"));
}
};
}
然后,您可以使用 Camel 中的 recommendations With 功能模拟单元测试中给定路由中的所有端点,如下所示:
使用 建议进行所有端点
@Test
public void testAdvisedMockEndpoints() throws Exception {
// advice the start route using the inlined AdviceWith lambda style route builder
// which has extended capabilities than the regular route builder
AdviceWith.adviceWith(context, "start", a ->
// mock all endpoints
a.mockEndpoints());
getMockEndpoint("mock:direct:start").expectedBodiesReceived("Hello World");
getMockEndpoint("mock:direct:foo").expectedBodiesReceived("Hello World");
getMockEndpoint("mock:log:foo").expectedBodiesReceived("Bye World");
getMockEndpoint("mock:result").expectedBodiesReceived("Bye World");
template.sendBody("direct:start", "Hello World");
assertMockEndpointsSatisfied();
// additional test to ensure correct endpoints in registry
assertNotNull(context.hasEndpoint("direct:start"));
assertNotNull(context.hasEndpoint("direct:foo"));
assertNotNull(context.hasEndpoint("log:foo"));
assertNotNull(context.hasEndpoint("mock:result"));
// all the endpoints was mocked
assertNotNull(context.hasEndpoint("mock:direct:start"));
assertNotNull(context.hasEndpoint("mock:direct:foo"));
assertNotNull(context.hasEndpoint("mock:log:foo"));
}
请注意,模拟端点被授予 URI mock:<endpoint>,如 mock:direct:foo。在 INFO 级别对被模拟的端点进行 Camel 日志:
INFO Adviced endpoint [direct://foo] with mock endpoint [mock:direct:foo]
模拟的端点没有参数
端点,这些端点会被模拟,其参数会剥离。例如,端点 log:foo?showAll=true 将被模拟到以下端点 mock:log:foo。请注意,删除了这些参数。
它还只能使用模式模拟某些端点。例如,模拟 您执行 的所有日志端点,如下所示:
建议 只使用一个模式模拟日志端点
@Test
public void testAdvisedMockEndpointsWithPattern() throws Exception {
// advice the start route using the inlined AdviceWith lambda style route builder
// which has extended capabilities than the regular route builder
AdviceWith.adviceWith(context, "start", a ->
// mock only log endpoints
a.mockEndpoints("log*"));
// now we can refer to log:foo as a mock and set our expectations
getMockEndpoint("mock:log:foo").expectedBodiesReceived("Bye World");
getMockEndpoint("mock:result").expectedBodiesReceived("Bye World");
template.sendBody("direct:start", "Hello World");
assertMockEndpointsSatisfied();
// additional test to ensure correct endpoints in registry
assertNotNull(context.hasEndpoint("direct:start"));
assertNotNull(context.hasEndpoint("direct:foo"));
assertNotNull(context.hasEndpoint("log:foo"));
assertNotNull(context.hasEndpoint("mock:result"));
// only the log:foo endpoint was mocked
assertNotNull(context.hasEndpoint("mock:log:foo"));
assertNull(context.hasEndpoint("mock:direct:start"));
assertNull(context.hasEndpoint("mock:direct:foo"));
}
支持的模式可以是通配符或正则表达式。请参阅 Intercept 将其与 Camel 使用的匹配功能相同的匹配功能的更多详情。
请记住,模拟端点会在消息到达模拟时复制消息。
这意味着 Camel 将使用更多内存。当您发送许多消息时,这可能不适用。