net.bluemind.calendar.sync.tests

Class CalendarSyncVerticleTests

java.lang.Object

net.bluemind.calendar.sync.tests.CalendarSyncVerticleTests

public class CalendarSyncVerticleTests
extends java.lang.Object

See Also:

CalendarSyncVerticle

Constructor Summary

Constructors

Constructor and Description
CalendarSyncVerticleTests()

Method Summary

Modifier and Type	Method and Description
void	before()
void	startIcsHttpServer()
void	teardown()
void	testBadIcsContent() Test updating a calendar with bad ICS content.
void	testETagChanges() Check we change the ICS content when the entity-tag (a.k.a.
void	testETagNoChange() Check we do not change the ICS content when the entity-tag (a.k.a.
void	testLastModifiedChanges() Check we change the ICS content when Last-Modified (If-Modified-Since) changes.
void	testLastModifiedGoogle() Check we do not update the ICS content when dealing with a google calendar which changes at each request because of the DTSTAMP line.
void	testLastModifiedModificationDateChanges() Check we change the ICS content when Content-Disposition/modification-date (If-Modified-Since) changes.
void	testLastModifiedModificationDateNoChange() Check we do not change the ICS content when the Content-Disposition/modification-date (If-Modified-Since) header does not change.
void	testLastModifiedNo304() Check we do not change the ICS content when lastModified timestamp has not changed even if we do not receive a 304 response status.
void	testLastModifiedNoChange() Check we do not change the ICS content when the Last-Modified (If-Modified-Since) header does not change.
void	testMd5NoChanges() Check we do not update a calendar when its MD5 checksum has not changed, even if we receive a 200 response.
void	testNextSyncExpireTomorrow() Check we do not sync when the Expire header is set to tomorrow. Note: 'Expire' races against the min delay (set in domain settings).
void	testNextSyncExpireYesterday() Check we do have a sync when the Expire header is set to yesterday.
void	testNextSyncMaxAgeTomorrow() Check we do not sync when the Cache-Control/max-age header is set to tomorrow. Note: 'max-age' races against the min delay (set in domain settings).
void	testNextSyncMaxAgeYesterday() Check we do have a sync when the Cache-Control/max-age header is set to yesterday.
void	testNoChanges() Trigger several times the sync for a never-changing ics ("MD5 mechanism" is triggered).
void	testPriority() Test the priority mechanism.
void	testTooManyChanges() Test an ICS with too much changes, it should not be sync-able the 4th time. Note: In this test, icsHttpServer will alternatively return a calendar with 51 events or just 1 each time a sync is requested (in order to reach the 'too much changes error' limit
void	testTooManyChangesShouldNotUseUnhandledEvents()
void	testWithChanges() Trigger several times the sync for a changing ics (one more event each time).
void	testWithChangesBigDelay() Due to a big minimum delay between synchronizations, no more than one sync should be done.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Constructor Detail

CalendarSyncVerticleTests

public CalendarSyncVerticleTests()

Method Detail

before

public void before()
            throws java.lang.Exception

Throws:

java.lang.Exception

startIcsHttpServer

public void startIcsHttpServer()

teardown

public void teardown()
              throws java.lang.Exception

Throws:

java.lang.Exception

testNoChanges

public void testNoChanges()
                   throws java.lang.InterruptedException

Trigger several times the sync for a never-changing ics ("MD5 mechanism" is triggered).

Throws:

java.lang.InterruptedException

testWithChanges

public void testWithChanges()
                     throws java.lang.Exception

Trigger several times the sync for a changing ics (one more event each time).

Throws:

java.lang.Exception

testWithChangesBigDelay

public void testWithChangesBigDelay()
                             throws java.lang.InterruptedException

Due to a big minimum delay between synchronizations, no more than one sync should be done.

Throws:

java.lang.InterruptedException

testTooManyChanges

public void testTooManyChanges()
                        throws java.lang.InterruptedException

Test an ICS with too much changes, it should not be sync-able the 4th time.
Note: In this test, icsHttpServer will alternatively return a calendar with 51 events or just 1 each time a sync is requested (in order to reach the 'too much changes error' limit

Throws:

java.lang.InterruptedException

testTooManyChangesShouldNotUseUnhandledEvents

public void testTooManyChangesShouldNotUseUnhandledEvents()
                                                   throws java.lang.InterruptedException

Throws:

java.lang.InterruptedException

testBadIcsContent

public void testBadIcsContent()
                       throws java.lang.InterruptedException

Test updating a calendar with bad ICS content. Change ICS content to avoid "MD5 mechanism".

Throws:

java.lang.InterruptedException

testETagNoChange

public void testETagNoChange()
                      throws java.lang.InterruptedException

Check we do not change the ICS content when the entity-tag (a.k.a. ETag) has not changed.

Throws:

java.lang.InterruptedException

testETagChanges

public void testETagChanges()
                     throws java.lang.InterruptedException

Check we change the ICS content when the entity-tag (a.k.a. ETag / If-None-Match)) changes.

Throws:

java.lang.InterruptedException

testLastModifiedNoChange

public void testLastModifiedNoChange()
                              throws java.lang.InterruptedException

Check we do not change the ICS content when the Last-Modified (If-Modified-Since) header does not change.

Throws:

java.lang.InterruptedException

testLastModifiedChanges

public void testLastModifiedChanges()
                             throws java.lang.InterruptedException

Check we change the ICS content when Last-Modified (If-Modified-Since) changes.

Throws:

java.lang.InterruptedException

testLastModifiedModificationDateNoChange

public void testLastModifiedModificationDateNoChange()
                                              throws java.lang.InterruptedException

Check we do not change the ICS content when the Content-Disposition/modification-date (If-Modified-Since) header does not change.

Throws:

java.lang.InterruptedException

testLastModifiedModificationDateChanges

public void testLastModifiedModificationDateChanges()
                                             throws java.lang.InterruptedException

Check we change the ICS content when Content-Disposition/modification-date (If-Modified-Since) changes.

Throws:

java.lang.InterruptedException

testLastModifiedNo304

public void testLastModifiedNo304()
                           throws java.lang.InterruptedException

Check we do not change the ICS content when lastModified timestamp has not changed even if we do not receive a 304 response status.

Throws:

java.lang.InterruptedException

testLastModifiedGoogle

public void testLastModifiedGoogle()
                            throws java.lang.InterruptedException

Check we do not update the ICS content when dealing with a google calendar which changes at each request because of the DTSTAMP line.

Throws:

java.lang.InterruptedException

testNextSyncExpireTomorrow

public void testNextSyncExpireTomorrow()
                                throws java.lang.InterruptedException

Check we do not sync when the Expire header is set to tomorrow.
Note: 'Expire' races against the min delay (set in domain settings). We always take the longer.

Throws:

java.lang.InterruptedException

testNextSyncExpireYesterday

public void testNextSyncExpireYesterday()
                                 throws java.lang.InterruptedException

Check we do have a sync when the Expire header is set to yesterday.

Throws:

java.lang.InterruptedException

testNextSyncMaxAgeTomorrow

public void testNextSyncMaxAgeTomorrow()
                                throws java.lang.InterruptedException

Check we do not sync when the Cache-Control/max-age header is set to tomorrow.
Note: 'max-age' races against the min delay (set in domain settings). We always take the longer.

Throws:

java.lang.InterruptedException

testNextSyncMaxAgeYesterday

public void testNextSyncMaxAgeYesterday()
                                 throws java.lang.InterruptedException

Check we do have a sync when the Cache-Control/max-age header is set to yesterday.

Throws:

java.lang.InterruptedException

testMd5NoChanges

public void testMd5NoChanges()
                      throws java.lang.InterruptedException

Check we do not update a calendar when its MD5 checksum has not changed, even if we receive a 200 response.

Throws:

java.lang.InterruptedException

testPriority

public void testPriority()

Test the priority mechanism. The less errors and the older syncs should go first. Error count is more important than last sync date.