Closed PamelaM closed 3 years ago
Well finally - insane integration test passes "well enough": Skipped: DJ 1.4 -> DJ 1.7 PY2.7 - DJ 1.8->DJ1.11tip all pass PY3.4 - DJ 1.8->DJ1.11tip all pass, DJ tip (2.0) Fails PY3.5 - DJ 1.8->DJ1.11tip all pass, DJ tip (2.0) Fails PY3.6 - DJ 1.8->DJ1.11tip all pass, DJ tip (2.0) Fails
I'm not going to worry about the DJ tip (2.0) failures for the moment. But will open a new branch that only include the fixes to the plugin
@PamelaM I'm not sure what our process is these days? Do you expect me to review pull requests? I looked through this: it's really something! :) I wonder if cookiecutter could be put to use helping with some of it.
Ancient, clutters my list of open PRs
NOT READY FOR REVIEW
Testing the complex and deferred initializations during django startup is pretty much impossible from within a standard unittest module. This PR is a first draft to add a test that programmatically (using subprocess.check_output calls) creates a django project and runs its unittests under coverage and checks that coverage matches expectations.
I suspect I might refactor the common insane_integration test into a gist or even a pypi package so that other django-packages could use it