List view

• v.1.4.4

  Goals: * Django 1.10 support * More options fixes * More REUSE_DB=1 fixes

  No due date

  •1/2 issues closed
  50% complete1 open1 closed

• Fix REUSE_DB=1

  REUSE_DB has many problems. It requires careful override of default Django test behavior, and the logic hasn't kept up-to-date with the Django test code. It will probably require a re-write of the code, and maybe should be extracted to it's own project. For now, document the bugs.

  No due date

  •1/14 issues closed
  7% complete13 open1 closed

• Fix FastFixtureTestCase

  FastFixtureTestCase is broken for many people.

  No due date

  •4/15 issues closed
  26% complete11 open4 closed

• Database Testing

  The django-nose test suite as of v1.4, April 2015, did not include database testing. This means that features such as `REUSE_DB=1` will continue to break, and only be discovered when used against other projects. Since v1.4.1, the following has been added: * Test settings to use [environment variables](http://12factor.net/config), to unify the various test cases into one config. * Database settings to use [dj-database-url](https://github.com/kennethreitz/dj-database-url), so that tests can run against different backends * Add models and model tests to [testapp](https://github.com/django-nose/django-nose/tree/master/testapp), so that database operations are exercised * Add test runs for `REUSE_DB=1` and similar options, to replicate failures. Now we have the infrastructure to fix database issues and detect problems with future Django versions.

  No due date
  0% complete0 open0 closed