Unit test – MULE MUNIT test case does not apply to APIKIT router flow

I have created a Munit test case for the flow generated by the APIKit router. But when running the test suite, I encountered the following exception:

< /p>

Exception in thread "main" java.lang.RuntimeException: org.mule.api.lifecycle.LifecycleException: null
at org.mule.munit.runner.mule.MunitSuiteRunner.( 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(NativeMethodAccessorI mpl.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.fireLifecycle(AbstractRegistryBroker. .java:76)
at org.mule.registry.MuleRegistryHelper.fireLifecycle(MuleRegistryHelper.java:136)
at org.mule.lifecycle.MuleContextLifecycleManager$MuleContextLifecycleCallback.onTransition(MuleContextLifecycleManager.java:91)< br /> at org.mule.lifecycle.MuleContextLifecycleMan ager$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.(MunitSuiteRunner.java:40)

Can anyone solve this problem? Thanks in advance.

You can try to add attributes like mock-connectors, mock-inbounds

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

The following is the munit:config tag modified in the munit configuration xml file.

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

I have passed APIKit The stream generated by the router creates the Munit test case. But when running the test suite, I encountered the following exception:

Exception in thread "main" java.lang. RuntimeException: org.mule.api.lifecycle.LifecycleException: null
at org.mule.munit.runner.mule.MunitSuiteRunner.(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.FlowConstru ctLifecycleManager.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(Abs tractRegistryBroker.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. (MunitSuiteRunner.java:40)

Can anyone solve this problem? Thanks in advance.

You can try to add attributes like mock-connectors, mock-inbounds

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

The following is the munit:config tag modified in the munit configuration xml file.

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

WordPress database error: [Table 'yf99682.wp_s6mz6tyggq_comments' doesn't exist]
SELECT SQL_CALC_FOUND_ROWS wp_s6mz6tyggq_comments.comment_ID FROM wp_s6mz6tyggq_comments WHERE ( comment_approved = '1' ) AND comment_post_ID = 1331 ORDER BY wp_s6mz6tyggq_comments.comment_date_gmt ASC, wp_s6mz6tyggq_comments.comment_ID ASC

Leave a Comment

Your email address will not be published.