org.mule.transport.sftp
Class SftpSendReceiveLargeFileFunctionalTestCase
java.lang.Object
org.mule.tck.junit4.AbstractMuleTestCase
org.mule.tck.junit4.AbstractMuleContextTestCase
org.mule.tck.junit4.FunctionalTestCase
org.mule.transport.sftp.AbstractSftpTestCase
org.mule.transport.sftp.SftpSendReceiveLargeFileFunctionalTestCase
public class SftpSendReceiveLargeFileFunctionalTestCase
- extends AbstractSftpTestCase
Test sending and receiving a very large message.
This test will probably fail due to the standard timeout. According to
http://www.mulesource.org/display/MULE2USER/Functional+Testing the only way to
change the timeout is "add -Dmule.test.timeoutSecs=XX either to the mvn command
you use to run Mule or to the JUnit test runner in your IDE." Tested with
'-Dmule.test.timeoutSecs=300'
Methods inherited from class org.mule.transport.sftp.AbstractSftpTestCase |
assertFilesInEndpoint, assertFilesInEndpoint, assertFilesInEndpoint, assertFilesInEndpoint, assertFilesInLocalFilesystem, assertFilesInLocalFilesystem, assertNoFilesInEndpoint, assertNoFilesInEndpoint, assertNoFilesInLocalFilesystem, checkConnectors, createRemoteDirectory, dispatchAndWaitForDelivery, dispatchAndWaitForException, dispatchAndWaitForException, executeBaseAssertionsAfterCall, executeBaseAssertionsBeforeCall, executeBaseTest, executeBaseTest, executeBaseTest, getAddressByEndpoint, getImmutableEndpoint, getPathByEndpoint, getSftpClient, getUriByEndpointName, initEndpointDirectories, initEndpointDirectory, isDisabledInThisEnvironment, recursiveDelete, recursiveDeleteInLocalFilesystem, remoteChmod, verifyFileExists, verifyFileExists |
Methods inherited from class org.mule.tck.junit4.AbstractMuleContextTestCase |
addBuilders, configureMuleContext, createMuleContext, createObject, createObject, disposeContext, disposeContextPerTest, doTearDown, getConfigurationResources, getSensingNullMessageProcessor, getStartUpProperties, getTestConnector, getTestEvent, getTestEvent, getTestEvent, getTestEvent, getTestEvent, getTestEvent, getTestEventContext, getTestEventContext, getTestEventUsingFlow, getTestInboundEndpoint, getTestInboundEndpoint, getTestInboundEndpoint, getTestInboundEndpoint, getTestInboundEndpoint, getTestInboundEvent, getTestInboundEvent, getTestInboundEvent, getTestOutboundEndpoint, getTestOutboundEndpoint, getTestOutboundEndpoint, getTestOutboundEndpoint, getTestOutboundEndpoint, getTestService, getTestService, getTestService, getTestSession, getTestTransactedInboundEndpoint, getTestTransformer, getTriggerableMessageSource, getTriggerableMessageSource, initialiseObject, isDisposeContextPerClass, isGracefulShutdown, isStartContext, setDisposeContextPerClass, setStartContext, setUpMuleContext |
Methods inherited from class org.mule.tck.junit4.AbstractMuleTestCase |
clearExcludedFlag, clearRequestContext, createTestTimeoutRule, getTestHeader, getTestTimeoutSecs, getTimeoutSystemProperty, initializeMuleTest, isDisabledInThisEnvironment, isExcluded, isFailOnTimeout, isOffline, isTestIncludedInExclusionFile |
Methods inherited from class java.lang.Object |
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait |
SftpSendReceiveLargeFileFunctionalTestCase
public SftpSendReceiveLargeFileFunctionalTestCase()
getConfigResources
protected String getConfigResources()
- Specified by:
getConfigResources
in class FunctionalTestCase
doSetUp
protected void doSetUp()
throws Exception
- Description copied from class:
AbstractMuleContextTestCase
- 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()
.
Under normal circumstances this method could be replace with a
@Before
annotated method.
- Overrides:
doSetUp
in class AbstractMuleContextTestCase
- Throws:
Exception
- if something fails that should halt the test case
testSendAndReceiveLargeFile
public void testSendAndReceiveLargeFile()
throws Exception
- Test sending and receiving a large file.
- Throws:
Exception
Copyright © 2003-2014 MuleSoft, Inc.. All Rights Reserved.