AbstractMuleTestCase providing access to a MuleContext instance and tools for manage it.AbstractMuleTestCase is a base class for Mule test cases.AbstractMuleContextTestCase to be used when a Processor or Flow that
implements both Processor.process(CoreEvent) and Processor.apply(Publisher) needs paramatized tests so that both
approaches are tested with the same test method.Processor that may performs processing during both the
request and response processing phases while supporting non-blocking execution.configName and asserts a failed
connectivity test.Publisher completion.PollingProber.check(long, long, CheckedSupplier) only that this one is expecting for the probe condition
to NEVER be met.TestsLogConfigurationHelper.configureLoggingForTest(Class)testClass resides.mockComponentLocatorError mock that will return the provided exception when calling Error.getCause()DataType's type, mime type and encoding.AbstractMuleContextTestCase.setUpMuleContext().AbstractMuleContextTestCase.disposeContextPerTest().Matcher for Either instances.Enumeration against a collection of expected items.Matcher for ErrorType instances.muleContext.Matcher for CoreEvent instances.Function.Function.getExceptionListeners method on the provided exception handler to avoid exposing that method on the public
API.getMessageProcessors method on the provided object to avoid exposing that method on the public API.TransformationService to get representation of a message for a given
DataTypeTransformationService to get representation of a message for a given
ClassTransformationService to get byte[] representation of a message.TransformationService to get a String representation of a message.Thread of the given nameMuleTestUtils.APPLE_FLOW..mule which are not deleted on each test case recycle.InMemoryObjectStore implements an optionally bounded in-memory store for message IDs with periodic expiry of old
entries.Optional is empty.String is equal to another string, regardless of the line breaks,helpful when dealing with
cross-platform testsJUnitProbe.test() and returns its outcome, provided that it didn't threw any Exception or
AssertionError.JUnitProbe which makes it Java 8 Lambda friendly.Probe for cases in which the JUnitProbe.isSatisfied() method can throw
exceptions or will perform JUnit/Hamcrest assertions, which result in AssertionErrorLifecycleTrackerProcessor that validates the phase transition being done on this component.Matcher for MessagingException instances.Matcher implementation for MetadataKeyMetadataKeyMatcherMuleContext to return testing services implementations.ExpressionExecutor.ConfigurationBuilder used to provide a mock implementation of ExtensionManager with an empty set of extensions.HttpService.context.TestTimeSupplier.timeInMillis by the given time which is expressed in the given unit.MuleContexts in unit tests.CoreEvent for each invocation.AbstractMuleContextTestCase.isGracefulShutdown() is false.Probe is satisfied or not.context to return the given value for the given key.context to return the given value for the given clazz.ByteBufferManagerScheduler implementation to be used in unit tests.SchedulerService implementation that provides a shared SimpleUnitTestSupportScheduler.ObjectStoreClassLoader for testing purposesCoreEvent instance for the scope of the current test method.MuleRegistry of a MuleContext.TimeSupplier for externalizing the system time.Matcher to easily test the structure of a ValueValueMatcherValueMatcherTestRule that checks for timeouts in the execution of the tests, but differently from the JUnit's
Timeout class, just prints a warning in the log and the test still pass.Statement to execute a test with a given timeout.Value parts to compare.Copyright © 2003–2018 MuleSoft, Inc.. All rights reserved.