Write a TCK for CalDAV4J about caldav4j

[GoogleCodeExporter]

As an example, as part of issue 18, I wrote a functional test 
FreeBusyQueryFunctionalTest.  This can be run against different server 
implementations once a mechanism to do so is decided upon.

Also, these slow running functional tests could be separated from the fast unit 
tests by configuring the Maven Surefire Plugin to run different executions.  A 
similar example is documented here:

http://www.sonatype.com/people/2009/06/integration-tests-with-maven-part-1-fails
afe-plugin/

Original comment by [email protected] on 22 Feb 2011 at 12:04

[GoogleCodeExporter]

I agree about the speed of the test. I think the main goal of caldav4j is to 
run successfully against various caldav implementation.

To have some internal test successful, but failing the interaction with a real 
caldav server, is a problem.

How can we manage this stuff?

Original comment by [email protected] on 22 Feb 2011 at 3:12

[GoogleCodeExporter]

1- added failsafe plugin
2- set @Ignore tag on method functional tests
3- add *ITCase on parameterized functional tests, to be run under all possible 
caldav server uris
4- TBD: what do you think to use an xml bean to configure the caldavcredential 
to test with?

Original comment by [email protected] on 26 Jul 2011 at 10:49

[TheAntimist]

This is good, but now that Google, has closed their public access to Caldav, and Chandler, not being there. Only Yahoo, seems to be the case to test, other than Bedework.

[ioggstream]

let's leave this around for some times more, then we can close as stale.

[TheAntimist]

sure