Tests: It's needed with some test-runs without `features` configured
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 48/100
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- Python
- Estrellas
- 412
- Forks
- 113
- Merge medio
- 10 h 29 min
- PR fusionados (30 d)
- 57
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de python-caldav/caldav
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
python-caldav/caldav#792 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
python-caldav/caldav#788 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
python-caldav/caldav#687 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 3/5 1-2 días Aptitud para principiantes 75/100
python-caldav/caldav#796 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
python-caldav/caldav#784 · 2 comentarios ·
Los mantenedores suelen responder en 1 día
Todos los issues de python-caldav/caldav
Issues similares
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
-
changelog investigate
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
ramnes/notion-sdk-py#423 ·
-
type-bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día