Skip to content

Database Testing

No due date 0% complete

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, to unify the various test cases into one config.
  • Database …

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, to unify the various test cases into one config.
  • Database settings to use dj-database-url, so that tests can run against different backends
  • Add models and model tests to 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.

There are no open issues in this milestone.

Add issues to milestones to help organize your work for a particular release or project.

Create new issue

Or find and add issues with no milestone in this repo.