Unit testing Mule Munit测试用例不适用于APIKit路由器流

Unit testing Mule Munit测试用例不适用于APIKit路由器流,unit-testing,mule,Unit Testing,Mule,我已经为通过APIKit路由器生成的流创建了Munit测试用例。但在运行测试套件时,我遇到了以下异常: Exception in thread "main" java.lang.RuntimeException: org.mule.api.lifecycle.LifecycleException: null at org.mule.munit.runner.mule.MunitSuiteRunner.<init>(MunitSuiteRunner.java:48) a

我已经为通过APIKit路由器生成的流创建了Munit测试用例。但在运行测试套件时,我遇到了以下异常:

Exception in thread "main" java.lang.RuntimeException: org.mule.api.lifecycle.LifecycleException: null
    at org.mule.munit.runner.mule.MunitSuiteRunner.<init>(MunitSuiteRunner.java:48)
    at org.mule.munit.runner.remote.MunitRemoteRunner.run(MunitRemoteRunner.java:40)
    at org.mule.munit.runner.remote.MunitRemoteRunner.main(MunitRemoteRunner.java:143)
Caused by: org.mule.api.lifecycle.LifecycleException: null
    at org.mule.lifecycle.AbstractLifecycleManager.invokePhase(AbstractLifecycleManager.java:153)
    at org.mule.construct.FlowConstructLifecycleManager.fireStartPhase(FlowConstructLifecycleManager.java:92)
    at org.mule.construct.AbstractFlowConstruct.start(AbstractFlowConstruct.java:136)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:606)
    at org.mule.lifecycle.phases.DefaultLifecyclePhase.applyLifecycle(DefaultLifecyclePhase.java:237)
    at org.mule.lifecycle.RegistryLifecycleManager$RegistryLifecycleCallback.onTransition(RegistryLifecycleManager.java:273)
    at org.mule.lifecycle.RegistryLifecycleManager.invokePhase(RegistryLifecycleManager.java:152)
    at org.mule.lifecycle.RegistryLifecycleManager.fireLifecycle(RegistryLifecycleManager.java:123)
    at org.mule.registry.AbstractRegistryBroker.fireLifecycle(AbstractRegistryBroker.java:76)
    at org.mule.registry.MuleRegistryHelper.fireLifecycle(MuleRegistryHelper.java:136)
    at org.mule.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:91)
    at org.mule.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:87)
    at org.mule.lifecycle.MuleContextLifecycleManager.invokePhase(MuleContextLifecycleManager.java:69)
    at org.mule.lifecycle.MuleContextLifecycleManager.fireLifecycle(MuleContextLifecycleManager.java:61)
    at org.mule.DefaultMuleContext.start(DefaultMuleContext.java:278)
    at org.mule.munit.runner.MuleContextManager.startMule(MuleContextManager.java:68)
    at org.mule.munit.runner.MuleContextManager.startMule(MuleContextManager.java:63)
    at org.mule.munit.runner.mule.MunitSuiteRunner.<init>(MunitSuiteRunner.java:40)
线程“main”java.lang.RuntimeException:org.mule.api.lifecycle.LifecycleException中的异常:null 位于org.mule.munit.runner.mule.MunitSuiteRunner.(MunitSuiteRunner.java:48) 位于org.mule.munit.runner.remote.MunitRemoteRunner.run(MunitRemoteRunner.java:40) 位于org.mule.munit.runner.remote.MunitRemoteRunner.main(MunitRemoteRunner.java:143) 原因:org.mule.api.lifecycle.LifecycleException:null 位于org.mule.lifecycle.AbstractLifecycleManager.InvokePase(AbstractLifecycleManager.java:153) 在org.mule.construct.FlowConstructLifecycleManager.fireStartPhase(FlowConstructLifecycleManager.java:92) 位于org.mule.construct.AbstractFlowConstruct.start(AbstractFlowConstruct.java:136) 在sun.reflect.NativeMethodAccessorImpl.invoke0(本机方法)处 在sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)中 在sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)中 位于java.lang.reflect.Method.invoke(Method.java:606) 位于org.mule.lifecycle.phases.DefaultLifecyclePase.applyLifecycle(DefaultLifecyclePase.java:237) 位于org.mule.lifecycle.RegistryLifecycleManager$RegistryLifecycleCallback.onTransition(RegistryLifecycleManager.java:273) 位于org.mule.lifecycle.RegistryLifecycleManager.InvokePase(RegistryLifecycleManager.java:152) 在org.mule.lifecycle.RegistryLifecycleManager.fireLifecycle(RegistryLifecycleManager.java:123) 位于org.mule.registry.AbstractRegistryBroker.fireLifecycle(AbstractRegistryBroker.java:76) 在org.mule.registry.MuleRegistryHelper.fireLifecycle上(MuleRegistryHelper.java:136) 位于org.mule.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:91) 位于org.mule.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:87) 位于org.mule.lifecycle.MuleContextLifecycleManager.invokePase(MuleContextLifecycleManager.java:69) 位于org.mule.lifecycle.MuleContextLifecycleManager.fireLifecycle(MuleContextLifecycleManager.java:61) 在org.mule.DefaultMuleContext.start(DefaultMuleContext.java:278) 位于org.mule.munit.runner.MuleContextManager.startMule(MuleContextManager.java:68) 在org.mule.munit.runner.MuleContextManager.startMule上(MuleContextManager.java:63) 位于org.mule.munit.runner.mule.MunitSuiteRunner.(MunitSuiteRunner.java:40)
谁能解决这个问题?提前感谢。

请尝试将模拟连接器、模拟内边界等属性添加到

配置

下面是munit配置xml文件中修改的munit:config标记


注意:我还没有在mUnit测试中使用任何mock,但是这个解决方案修复了错误。对我来说也是如此!谢谢,谢谢!这在Mule文档或教程中并不明显。