Caldav test servers
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
調査の方向性
The issue names the caldav-server-tester and the Python and Docker test-server setup, but does not identify files or a specific implementation task. First read the test framework and its existing server configuration to understand how external servers are exercised. Done would require a concrete new server or test-account contribution; the issue currently asks broadly for credentials and server suggestions rather than defining one.
索引モデルが issue の本文から書いたものです。
説明
This was last updated 2026-03-08, between v3.0.0 and v3.0.1
Call for help
I need servers to test the library with!
The library is now relatively well-tested towards open source servers, but it's not much tested towards cloud servers. I don't want to run around signing up at different services and installing test servers myself. 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. Even just running the caldav-server-tester and give me the results is better than nothing.
The credentials plus contact information will be kept in a plain text config file ("encryption on rest" on the storage/file system level) on a private server of mine and on my laptop, plus possibly 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 towards external servers will be run ad-hoc when working towards releases.
The test code spawn quite a lot of communication, as it (tries to) make sure all previously used test calendars are properly deleted bwtween every test. Please get in touch with me if this is an issue for you. I do have some rate-limiting options in the test setup.
Contributing with access to a test account is a win-win-situation, as you can be sure exactly your server is regularly tested.
Even if I now have a battery of docker-containers with various open source servers that I'm testing towards, it's still useful to test towards extra external servers. Things may work sweet towards a local docker instance, but still frequently users reports the strangest problems on the issue tracker - real world servers may not run the same version as the docker test framework, the configuration may vary, the configuration of other components like proxying through nginx - even server latency may cause issues.
Test servers included in the framework
Tests are regularly done towards those servers:
Built-in python test servers:
- Xandikos
- Radicale
Docker-based servers:
- Baikal
- Bedework
- Apple CalendarServer (CCS) - docker
- Cyrus
- DAViCal
- Davis
- NextCloud
- Open eXange (not very well-tested due to serious compatibility issues)
- SOGo
- Stalwart
- Zimbra
The python tests will run if the python package is installed and available in PYTHONPATH. The docker-based servers will be tested if Docker is available.
I'm currently not aware of other significant open source servers, except for Robur. Robur does not fit very well into the testing framework.
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.
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)
Robur is also available for the public, but I'm keeping a dedicated username/password in my "private" config.
Private test servers actively used
(More or less) stable test servers
A bit on and off, but my "battery" of private testing accounts includes:
- DAViCal
- eCloud
- Zimbra (will be discontinued due to license problems)
- Synology
- Purelymail
- Robur
- Posteo
- GMX (a 3.0 pre-release tested OK, but when testing 3.0 it was spewing authentication errors - I haven't looked more into it)
Long time ago (varying for the servers below, but for some it even means "before the 1.0 release") the library has also been tested towards:
- Different Nextcloud versions and installations
- iCloud
- Google (but only their deprecated endpoint as for now)
- Fastmail
- Lark
- all-inkl.com
- calendar.mail.ru
Other test servers currently missing
... not aware of any, but please inform!
**Please help! Donate credentials for working test account(s) on YOUR caldav server! **
- 主要言語
- Python
- スター
- 412
- フォーク
- 113
- 平均マージ
- 1日 2時間
- マージ済み PR（30日）
- 43
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートなし
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
python-caldav/caldav のほかの issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 62/100
python-caldav/caldav#687 ·
メンテナーはふだん 1 日以内に返信
-
難易度 3/5 1〜2日 初心者へのやさしさ 55/100
python-caldav/caldav#780 ·
メンテナーはふだん 1 日以内に返信
-
compatibility refactoring
難易度 4/5 3〜5日 初心者へのやさしさ 32/100
python-caldav/caldav#778 · コメント 2 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 5/5 1週間以上 初心者へのやさしさ 18/100
python-caldav/caldav#777 ·
メンテナーはふだん 1 日以内に返信
-
難易度 4/5 3〜5日 初心者へのやさしさ 25/100
python-caldav/caldav#774 ·
メンテナーはふだん 1 日以内に返信
python-caldav/caldav の issue をすべて見る
似ている issue
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
jbacalso24/mimry#291 ·
メンテナーはふだん 1 日以内に返信
-
good first issue
難易度 2/5 1時間未満 初心者へのやさしさ 82/100
eli-alvarado/us-watchlist-alerts#14 ·
メンテナーはふだん 1 日以内に返信
-
from-review-extraction python severity:nit
難易度 2/5 1〜3時間 初心者へのやさしさ 80/100
LearningCircuit/local-deep-research#7462 ·
メンテナーはふだん 2 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
cathrynlavery/diagram-design#441 ·
メンテナーはふだん 2 日以内に返信
-
[Cleanup] Include the public header in work_split.cpp対応中かも @blozano-tt が今日担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
tenstorrent/tt-metal#60850 ·
メンテナーはふだん 1 日以内に返信