gpt4 book ai didi

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

转载 作者:行者123 更新时间:2023-12-02 01:30:40 24 4
gpt4 key购买 nike

我已经为通过 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)

谁能解决这个问题吗?提前致谢。

最佳答案

您可以尝试添加诸如mock-connectors、mock-inbounds之类的属性吗

<munit:config doc:name="Munit configuration"/>配置

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

<munit:config doc:name="Munit configuration" mock-connectors="false" mock-inbounds="false"/>

关于unit-testing - Mule Munit 测试用例不适用于 APIKit 路由器流,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/28576351/

24 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com