Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Tests: It's needed with some test-runs without `features` configured

Aperta
  • Qualcosa non va?
#725 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
python
Ambito
testing

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
Python
Stelle
412
Fork
113
Merge medio
22h 43m
PR unite (30g)
43

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di python-caldav/caldav

Tutte le issue di python-caldav/caldav

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.