public abstract class AbstractReactiveProcessorTestCase extends AbstractMuleContextTestCase
AbstractMuleContextTestCase to be used when a Processor or
Flow that implements both Processor.process(Event) and
Processor.apply(Publisher) needs paramatized tests so that both approaches are tested with the same test method. Test
cases that extend this abstract class should use (@link process(Processor, Event) to invoke Processor's as
part of the test, rather than invoking them directly.| Modifier and Type | Class and Description |
|---|---|
static class |
AbstractReactiveProcessorTestCase.Mode |
| Modifier and Type | Field and Description |
|---|---|
protected AbstractReactiveProcessorTestCase.Mode |
mode |
protected org.mule.runtime.api.scheduler.Scheduler |
scheduler |
BLOCK_TIMEOUT, callbackCalled, IGNORED_DOT_MULE_DIRS, LOCK_TIMEOUT, muleContext, REACTOR_BLOCK_TIMEOUT_EXCEPTION_MESSAGE, RECEIVE_TIMEOUT, TEST_MESSAGE, WORKING_DIRECTORY_SYSTEM_PROPERTY_KEY, workingDirectoryDEFAULT_TEST_TIMEOUT_SECS, globalTimeout, logger, name, TEST_CONNECTOR, TEST_PAYLOAD, TEST_TIMEOUT_SYSTEM_PROPERTY, TESTING_MODE_PROPERTY_NAME| Constructor and Description |
|---|
AbstractReactiveProcessorTestCase(AbstractReactiveProcessorTestCase.Mode mode) |
| Modifier and Type | Method and Description |
|---|---|
protected void |
doSetUp()
Enables the adding of extra behavior on the set up stage of a test right after the creation of the mule context in
AbstractMuleContextTestCase.setUpMuleContext(). |
protected void |
doTearDown()
Enables the adding of extra behavior on the tear down stage of a test before the mule context is disposed in
AbstractMuleContextTestCase.disposeContextPerTest(). |
static Collection<Object[]> |
parameters() |
protected Event |
process(Processor processor,
Event event) |
addBuilders, configureMuleContext, createMuleContext, createObject, createObject, disposeContext, disposeContextPerTest, doSetUpBeforeMuleContextCreation, doTearDownAfterMuleContextDispose, eventBuilder, getBuilder, getConfigurationResources, getExecutionClassLoader, getFileInsideWorkingDirectory, getObjectSerializer, getPayload, getPayload, getPayloadAsBytes, getPayloadAsString, getPayloadAsString, getSensingNullMessageProcessor, getStartUpProperties, getTestFlowWithComponent, getTriggerableMessageSource, getWorkingDirectory, initialiseObject, isDisposeContextPerClass, isGracefulShutdown, isStartContext, mockHttpService, setDisposeContextPerClass, setStartContext, setUpMuleContext, verifyAndStopSchedulersclearRequestContext, clearTestCaseName, clearTestEvents, collectThreadNames, createTestTimeoutRule, dumpFilteredThreadsInTest, getMavenProjectVersionProperty, getTestHeader, getTestTimeoutSecs, getTimeoutSystemProperty, initializeMuleTest, isDisabledInThisEnvironment, isDisabledInThisEnvironment, isFailOnTimeout, isOffline, nullPayloadEvent, takeTestCaseName, testEventprotected org.mule.runtime.api.scheduler.Scheduler scheduler
protected AbstractReactiveProcessorTestCase.Mode mode
public AbstractReactiveProcessorTestCase(AbstractReactiveProcessorTestCase.Mode mode)
public static Collection<Object[]> parameters()
protected void doSetUp()
throws Exception
AbstractMuleContextTestCaseAbstractMuleContextTestCase.setUpMuleContext().
Under normal circumstances this method could be replaced by a @Before annotated method.
doSetUp in class AbstractMuleContextTestCaseException - if something fails that should halt the test caseprotected void doTearDown()
throws Exception
AbstractMuleContextTestCaseAbstractMuleContextTestCase.disposeContextPerTest().
Under normal circumstances this method could be replace with a @After annotated method.
doTearDown in class AbstractMuleContextTestCaseException - if something fails that should halt the testcaseCopyright © 2003–2017 MuleSoft, Inc.. All rights reserved.