AbstractMuleTestCase (Mule Core 2.0.0-RC2 API)

Overview

Package

Class

Use

Tree

Deprecated

Index

Help

PREV CLASS NEXT CLASS

FRAMES NO FRAMES

SUMMARY: NESTED | FIELD | CONSTR | METHOD

DETAIL: FIELD | CONSTR | METHOD

org.mule.tck
Class AbstractMuleTestCase

java.lang.Object
  junit.framework.Assert
      junit.framework.TestCase
          org.mule.tck.AbstractMuleTestCase

All Implemented Interfaces:: Test, TestCaseWatchdogTimeoutHandler

Direct Known Subclasses:: AbstractConnectorTestCase, AbstractContainerContextTestCase, AbstractMessageAdapterTestCase, AbstractMessageReceiverTestCase, AbstractTransformerTestCase, AbstractTxThreadAssociationTestCase

public abstract class AbstractMuleTestCase
extends TestCase
implements TestCaseWatchdogTimeoutHandler
extends TestCase
implements TestCaseWatchdogTimeoutHandler

AbstractMuleTestCase is a base class for Mule testcases. This implementation provides services to test code for creating mock and test objects.

Nested Class Summary
`static class`	`AbstractMuleTestCase.TestInfo`

Field Summary
`protected Latch`	`callbackCalled` Use this as a semaphore to the unit test to indicate when a callback has successfully been called.
`static String[]`	`IGNORED_DOT_MULE_DIRS` Top-level directories under `.mule` which are not deleted on each test case recycle.
`static long`	`LOCK_TIMEOUT` Default timeout for multithreaded tests (using CountDownLatch, WaitableBoolean, etc.), in milliseconds.
`protected Log`	`logger`
`protected static MuleContext`	`muleContext`
`static String`	`TEST_MESSAGE` Convenient test message for unit testing.

Constructor Summary
`AbstractMuleTestCase()`

Method Summary
`protected MuleContext`	`createMuleContext()`
`protected AbstractMuleTestCase.TestInfo`	`createTestInfo()`
`protected TestCaseWatchdog`	`createWatchdog()`
`protected void`	`disposeManager()`
`protected void`	`doSetUp()`
`protected void`	`doTearDown()`
`protected ConfigurationBuilder`	`getBuilder()`
`protected String`	`getConfigurationResources()`
`String`	`getName()`
`protected Properties`	`getStartUpProperties()`
`static TestConnector`	`getTestConnector()`
`static MuleEvent`	`getTestEvent(Object data)`
`static MuleEvent`	`getTestEvent(Object data, ImmutableEndpoint endpoint)`
`static MuleEvent`	`getTestEvent(Object data, Service service)`
`static MuleEvent`	`getTestEvent(Object data, Service service, ImmutableEndpoint endpoint)`
`static MuleEventContext`	`getTestEventContext(Object data)`
`static Endpoint`	`getTestInboundEndpoint(String name)`
`protected AbstractMuleTestCase.TestInfo`	`getTestInfo()`
`static Endpoint`	`getTestOutboundEndpoint(String name)`
`static Service`	`getTestService()`
`static Service`	`getTestService(String name, Class clazz)`
`static Service`	`getTestService(String name, Class clazz, Map props)`
`static MuleSession`	`getTestSession(Service service)`
`static Transformer`	`getTestTransformer()`
`void`	`handleTimeout(long timeout, edu.emory.mathcs.backport.java.util.concurrent.TimeUnit unit)`
`protected boolean`	`isDisabledInThisEnvironment()` Subclasses can override this method to skip the execution of the entire test class.
`protected boolean`	`isDisabledInThisEnvironment(String testMethodName)` Should this test run?
`protected boolean`	`isDisposeManagerPerSuite()`
`protected boolean`	`isExcluded()` Indicates whether this test has been explicitly disabled through the configuration file loaded by TestInfo.
`boolean`	`isOffline(String method)`
`protected boolean`	`isStartContext()`
`protected void`	`registerTestMethod()`
`void`	`run(TestResult result)`
`void`	`runBare()` Shamelessly copy from Spring's ConditionalTestCase so in MULE-2.0 we can extend this class from ConditionalTestCase.
`protected void`	`setDisposeManagerPerSuite(boolean val)`
`void`	`setName(String name)`
`protected void`	`setStartContext(boolean startContext)`
`protected void`	`setUp()`
`protected void`	`suitePostTearDown()` Run after all testcase teardowns.
`protected void`	`suitePreSetUp()` Run before any testcase setup.
`protected void`	`tearDown()`

Methods inherited from class junit.framework.TestCase
`countTestCases, createResult, run, runTest, toString`

Methods inherited from class junit.framework.Assert
`assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertFalse, assertFalse, assertNotNull, assertNotNull, assertNotSame, assertNotSame, assertNull, assertNull, assertSame, assertSame, assertTrue, assertTrue, fail, fail, failNotEquals, failNotSame, failSame`

Methods inherited from class junit.framework.Assert

assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertEquals, assertFalse, assertFalse, assertNotNull, assertNotNull, assertNotSame, assertNotSame, assertNull, assertNull, assertSame, assertSame, assertTrue, assertTrue, fail, fail, failNotEquals, failNotSame, failSame

Methods inherited from class java.lang.Object
`clone, equals, finalize, getClass, hashCode, notify, notifyAll, wait, wait, wait`

Field Detail

IGNORED_DOT_MULE_DIRS

public static final String[] IGNORED_DOT_MULE_DIRS

Top-level directories under .mule which are not deleted on each test case recycle. This is required, e.g. to play nice with transaction manager recovery service object store.

muleContext

protected static MuleContext muleContext

logger

protected final transient Log logger

TEST_MESSAGE

public static final String TEST_MESSAGE

Convenient test message for unit testing.

See Also:: Constant Field Values

LOCK_TIMEOUT

public static final long LOCK_TIMEOUT

Default timeout for multithreaded tests (using CountDownLatch, WaitableBoolean, etc.), in milliseconds. The higher this value, the more reliable the test will be, so it should be set high for Continuous Integration. However, this can waste time during day-to-day development cycles, so you may want to temporarily lower it while debugging.

See Also:: Constant Field Values

callbackCalled

protected Latch callbackCalled

Use this as a semaphore to the unit test to indicate when a callback has successfully been called.

Constructor Detail