public class FolderSyncEndpointTests extends AbstractEndpointTest
device, devId, devType, domainUid, endpoint, lastAsyncResponse, login, owner, password, reqFactory, testDevice, vmHostname| Constructor and Description | 
|---|
FolderSyncEndpointTests()  | 
| Modifier and Type | Method and Description | 
|---|---|
WbxmlHandlerBase | 
createEndpoint()  | 
void | 
testEmptyDocument()
Checks that even if the request is clearly broken, we get at least an error
 response. 
 | 
void | 
testIncrementalFolderSync()  | 
void | 
testInitialFolderSync()
This one should work. 
 | 
void | 
testInvalidXmlFolderSync()
This one should be rejected by schema  
Validator | 
appendEmail, appendEmail, appendEml, fetchEmail, newDocument, rmAddedMails, runEndpoint, runEndpoint, runEndpoint, runEndpointNoBody, setUp, stream, tearDown, updateMessageassertEquals, 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, countTestCases, createResult, fail, fail, failNotEquals, failNotSame, failSame, format, getName, run, run, runBare, runTest, setName, toStringpublic void testEmptyDocument()
WbxmlHandlerBase as the wbxml fails to
 parse.public void testInvalidXmlFolderSync()
Validatorpublic void testInitialFolderSync()
Validator, we
 don't need to check it.public void testIncrementalFolderSync()
                               throws java.lang.Exception
java.lang.Exceptionpublic WbxmlHandlerBase createEndpoint()
createEndpoint in class AbstractEndpointTestCopyright © 2023. All Rights Reserved.