cookiecutter/cookiecutter-django

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

Open

#810 opened on Sep 20, 2016

View on GitHub
 (1 comment) (3 reactions) (0 assignees)Python (10,896 stars) (2,713 forks)batch import
help wanted

Description

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.

Contributor guide

Tech stack
pythondjango
Domain
backendtesting
Issue type
test
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
PythonDjangocookiecutterpytest
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
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.