Tests: It's needed with some test-runs without `features` configured
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start by reviewing the existing integration tests and compatibility-hint/workaround paths in the caldav library; the issue does not name specific files. Identify workarounds expected to work without features, add integration coverage using a davclient object stripped of feature configuration, and run those tests against the relevant server scenarios. Done means regressions in the no-features use case are covered.
由索引模型根据 Issue 内容生成。
描述
I've "always" had workarounds for non-compliant servers in the caldav library.
The "compatibility flags" was originally meant only to skip integration tests on servers not supporting certain features. Later it got reorganized, renamed into "compatibility hints" and is now also used in the library itself for enabling/disabling some workarounds (notably in the search functionality). However, most of the workarounds are kicking in automatically when needed.
For all the integration testing done today, features is specified. This is contrary to the common use-case where the server is only configured with username and password, but without features - hence regressions like #722 was not caught. #713 is also an issue that couldn't be tested within the current test framework (even if #720 is fixed). The upcoming 3.4-release has a known regression for some combos of use-case scenarios and servers if not specifying the features-flag - but it had to be tested and verified manually, and who knows how many other unknown regressions there are.
It's needed to get an overview of all the workarounds that "should work even without features configured", make integration test code for it, and run those tests towards a patched davclient object stripped of the features-configuration.
- 主要语言
- Python
- 星标
- 412
- 派生
- 113
- 平均合并
- 10 小时 34 分钟
- 30 天内合并 PR
- 75
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
python-caldav/caldav 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
python-caldav/caldav#792 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
python-caldav/caldav#788 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
python-caldav/caldav#687 ·
维护者通常 1 天内回复
-
难度 4/5 3-5 天 新手友好度 48/100
python-caldav/caldav#829 · 1 条评论 ·
维护者通常 1 天内回复
-
ical + caldav未关闭
难度 5/5 一周以上 新手友好度 25/100
python-caldav/caldav#825 · 1 条评论 ·
维护者通常 1 天内回复
查看 python-caldav/caldav 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 79/100
aws-samples/sample-per-model-bedrock#639 ·
维护者通常 1 天内回复
-
bug
难度 1/5 1 小时以内 新手友好度 86/100
awslabs/visual-asset-management-system#937 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 79/100
project-codeflare/codeflare-sdk#1195 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
pandas-dev/pandas-stubs#2051 ·
维护者通常 1 天内回复