public class SftpArchiveFunctionalTestCase extends AbstractSftpTestCase
AbstractSftpTestCase.DispatchParameters
AbstractServiceAndFlowTestCase.ConfigVariant
FILENAME, INBOUND_ENDPOINT_DIR, MESSAGE_PROPERTIES, OUTBOUND_ENDPOINT_DIR, port, sftpClient, sftpServer
configResources, variant
callbackCalled, CLASSNAME_ANNOTATIONS_CONFIG_BUILDER, IGNORED_DOT_MULE_DIRS, LOCK_TIMEOUT, muleContext, RECEIVE_TIMEOUT, TEST_MESSAGE, TEST_PAYLOAD, WORKING_DIRECTORY_SYSTEM_PROPERTY_KEY, workingDirectory
DEFAULT_TEST_TIMEOUT_SECS, globalTimeout, logger, name, TEST_TIMEOUT_SYSTEM_PROPERTY, TESTING_MODE_PROPERTY_NAME
Constructor and Description |
---|
SftpArchiveFunctionalTestCase(AbstractServiceAndFlowTestCase.ConfigVariant variant,
String configResources) |
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() . |
static Collection<Object[]> |
parameters() |
void |
testArchive1()
Test plain archive functionality with no extra features enabled
|
void |
testArchive2()
Test archive functionality with full usage of temp-dir and creation of unique
names of temp-files
|
void |
testArchive3()
Test archive functionality with usage of temp-dir for inbound and outbound
endpoints with creation of unique names of temp-files but not for the archive
|
void |
testArchive4()
Test archive functionality with usage of temp-dir for archive but not for
inbound and outbound endpoints
|
void |
testCantWriteToArchive1()
Test error handling with plain archive functionality with no extra features
enabled
|
void |
testCantWriteToArchive2()
Test error handling with archive functionality with full usage of temp-dir and
creation of unique names of temp-files
|
void |
testCantWriteToArchive3()
Test error handling with archive functionality with usage of temp-dir for
inbound and outbound endpoints with creation of unique names of temp-files but
not for the archive
|
void |
testCantWriteToArchive4()
Test error handling with archive functionality with usage of temp-dir for
archive but not for inbound and outbound endpoints
|
assertFilesInEndpoint, assertFilesInEndpoint, assertFilesInEndpoint, assertFilesInEndpoint, assertFilesInLocalFilesystem, assertFilesInLocalFilesystem, assertNoFilesInEndpoint, assertNoFilesInEndpoint, assertNoFilesInLocalFilesystem, before, checkConnectors, createRemoteDirectory, dispatchAndWaitForDelivery, dispatchAndWaitForException, dispatchAndWaitForException, executeBaseAssertionsAfterCall, executeBaseAssertionsBeforeCall, executeBaseTest, executeBaseTest, executeBaseTest, getAddressByEndpoint, getImmutableEndpoint, getPathByEndpoint, getSftpClient, getSftpClient, getUriByEndpointName, initEndpointDirectories, initEndpointDirectory, recursiveDelete, recursiveDeleteInLocalFilesystem, remoteChmod, verifyFileExists, verifyFileExists
doSetUpForFlow, doSetUpForService, getConfigFile, getConfigFiles, getTestHeader
clearFlowAssertions, getBuilder, getComponent, getComponent, getConfigResources, getFlowConstruct, getFunctionalTestComponent, getSubFlow, loadResource, loadResourceAsString, lookupFlowConstruct, runFlow, runFlow, runFlow, runFlowAndExpect, runFlowAndExpectProperty, runFlowWithPayloadAndExpect, runSchedulersOnce, stopFlowConstruct, stopFlowSchedulers, testFlow, testFlow
addBuilders, configureMuleContext, createMuleContext, createObject, createObject, disposeContext, disposeContextPerTest, doSetUpBeforeMuleContextCreation, doTearDown, doTearDownAfterMuleContextDispose, getConfigurationResources, getFileInsideWorkingDirectory, getSensingNullMessageProcessor, getStartUpProperties, getTestConnector, getTestEvent, getTestEvent, getTestEvent, getTestEvent, getTestEvent, getTestEvent, getTestEvent, getTestEvent, getTestEventContext, getTestEventContext, getTestEventUsingFlow, getTestInboundEndpoint, getTestInboundEndpoint, getTestInboundEndpoint, getTestInboundEndpoint, getTestInboundEndpoint, getTestMuleMessage, getTestOutboundEndpoint, getTestOutboundEndpoint, getTestOutboundEndpoint, getTestOutboundEndpoint, getTestOutboundEndpoint, getTestService, getTestService, getTestService, getTestSession, getTestTransactedInboundEndpoint, getTestTransformer, getTriggerableMessageSource, getTriggerableMessageSource, getWorkingDirectory, initialiseObject, isDisposeContextPerClass, isGracefulShutdown, isStartContext, setDisposeContextPerClass, setStartContext, setUpMuleContext
clearExcludedFlag, clearRequestContext, clearTestCaseName, createTestTimeoutRule, dumpFilteredThreadsInTest, getTestTimeoutSecs, getTimeoutSystemProperty, initializeMuleTest, isDisabledInThisEnvironment, isDisabledInThisEnvironment, isExcluded, isFailOnTimeout, isOffline, isTestIncludedInExclusionFile, takeTestCaseName
public SftpArchiveFunctionalTestCase(AbstractServiceAndFlowTestCase.ConfigVariant variant, String configResources)
public static Collection<Object[]> parameters()
protected void doSetUp() throws Exception
AbstractMuleContextTestCase
AbstractMuleContextTestCase.setUpMuleContext()
.
Under normal circumstances this method could be replaced by a
@Before
annotated method.
doSetUp
in class AbstractServiceAndFlowTestCase
Exception
- if something fails that should halt the test casepublic void testArchive1() throws Exception
Exception
public void testArchive2() throws Exception
Exception
public void testArchive3() throws Exception
Exception
public void testArchive4() throws Exception
Exception
public void testCantWriteToArchive1() throws Exception
Exception
public void testCantWriteToArchive2() throws Exception
Exception
public void testCantWriteToArchive3() throws Exception
Exception
Copyright © 2003–2015 MuleSoft, Inc.. All rights reserved.