cookiecutter/cookiecutter-django

Add test to ensure that generated app runs and has 100% test coverage

Open

Aperta il 20 set 2016

Vedi su GitHub
 (1 commento) (3 reazioni) (0 assegnatari)Python (10.896 star) (2713 fork)batch import
help wanted

Descrizione

As per a note on the Django 1.10 release, pulling out into its own issue.

The tests passed, but the generated app wouldn't run on the 1.10 release.

Also, testing the claim of "generating a Django project that has 100% test coverage out of the box."

IOW, not cookiecutter-django itself, but the project generated therefrom.

So, as part of the tests, we generate a project, then ensure that it runs and has 100% test coverage.

Guida contributor

Tech stack
pythondjango
Dominio
backendtesting
Tipo issue
test
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
3
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
1-3 hours
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
stale
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
clear
Prerequisiti
PythonDjangocookiecutterpytest
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
65
Direzione di ricerca
Examine the existing test suite in the repository (likely in tests/ directory). Understand how cookiecutter tests are structured, possibly using pytest cookies. The issue mentions that the generated app failed to run on Django 1.10, so ensure compatibility. Write a test that generates a project from the template, then runs its test suite (e.g., `python manage.py test`) and verifies 100% coverage (e.g., with coverage.py). Look at the cookiecutter.json and post gen project.py for configuration.