feature request, improving tests with pytest and pytest-vcr
- Lenguaje dominante
- Python
- Estrellas
- 2.1k
- Forks
- 931
- Merge medio
- 1 d 2 h
- PR fusionados (30 d)
- 4
Descripción
## Feature Permission Request
Hi, there. Please keep in mind:
- my English is very poor
- I have a very limited experience with any open source projects, especially this one
Recently I'v made a small changes to some cloud providers:
- https://github.com/apache/libcloud/pull/1508 (Digitalocean)
- https://github.com/apache/libcloud/pull/1506 (Vultr)
I am asking for permission for completely rewrite some tests with:
- https://docs.pytest.org/en/stable/
- https://pytest-vcr.readthedocs.io/en/latest/
I chose Vultr for a start point for me.
I believe that `pytest` is a very nice and easiest way to write any tests for any project. Many people do not like write tests, but with `pytest` and `pytest-vcr` their work will be more funny and much better.
I can not promise that my work will be done completely, but I will try to make a start point for that.
Please suggest me the write way. E.g.:
- I should not make any changes to current tests
- I should make new tests from the scratch
P.S.
I hope Google translate is working as expected :smiley:
Guía de contribución
Línea de trabajo
Comienza revisando las pruebas existentes del proveedor Vultr y, después, lee la documentación enlazada de pytest y pytest-vcr. El issue no identifica archivos de pruebas ni un alcance definido, así que primero determina si las pruebas de Vultr deben reescribirse o complementarse. Para darlo por terminado, se requiere un enfoque acordado y una suite de pruebas exitosa para la cobertura seleccionada.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- python
- Área
- cloud, testing
- Tipo de issue
- Nueva funcionalidad
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 25/100