This was last updated 2022-04-24, prior to the v0.9-release
Call for help
I need servers to test the library with!
To be able to release the caldav library with the least amount of regression issues, I need to be able to run the test suite towards as many calendar servers as possible. While I may be able to set up and maintain a few calendar servers and cloud accounts myself, I don't really have the time nor capacity to cover everything myself. It's quite outside the scope of the caldav library maintenance. I need your help supplying me with test accounts I can use - an URL, a username, a password and a short description of what kind of server I will find. I expect the accounts given to work on a long term, but ad-hoc access when doing research on bugs or when doing releases may also work out.
The credentials plus contact information will be kept unencrypted ("encryption on rest" on the storage/file system level) on a private server of mine and on my laptop, plus an encrypted backup. It will only be used for running the test suite. The testing will create test calendars and will delete them when done, it should not touch any calendaring data on the account (though no guarantees given), I'm using my personal calendaring accounts on some systems.
Tests will be run ad-hoc when working towards releases, by average probably around once a day.
The test code spawn quite a lot of communication, as it makes sure all previously used test calendars are properly deleted before every test. I should probably refactor this code. Please get in touch with me if this is an issue for you.
Contributing with access to a test account is a win-win-situation, as you can be sure exactly your server is regularly tested.
Local test servers
If installed, those python-based servers will be spawned up locally by the test framework:
Those are run directly from the pyhon-code, hence they have to be available in the PYTHONPATH of the python version being used when running tests.
Public test servers
My plan was to manage some public test servers, and at some point I had some of them running - but currently this idea is shelved. I also had the alternative idea to create some script to spin up servers locally using docker. Perhaps at some point in the future ...
Nextcloud has a public test server ... from https://try.nextcloud.com/ it's possible to generate a username that is valid for one hour (should probably try looking into automating things here)
Private test servers
The v0.9 was tested against those: (work in progress)
- Nextcloud (several implementations)
- eCloud (but also a NextCloud clone, I believe)
- Baikal
- Zimbra
- DAViCal (older version)
Earlier test servers
Those has been tested at some earlier point in history, but the 0.9-release was not tested against those:
- SOGo
- Bedework
- iCloud
- Google (but only their deprecated endpoint as for now)
- Fastmail
Test servers currently missing
- Open eXchange
- up-to-date versions of DAViCal
- Googles new caldav endpoints
- The now abandoned Apple CalendarServer project
Others?
Other
Only python 3.10 and python 3.8 tested as of the 0.9-release.
Should eventually look through https://en.wikipedia.org/wiki/Comparison_of_CalDAV_and_CardDAV_implementations#Server_implementations