Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Django test runner using nose
Python Shell Makefile

REUSE_DB=1 tests run but are allowed to fail

There are many issues with REUSE_DB=1, including intermittant failures.
This allows us to monitor them and try to make them repeatable, but
without blocking other changes.
latest commit 5ad928ec94
@jwhitlock jwhitlock authored

README.rst

django-nose

The PyPI package PyPI download statistics https://travis-ci.org/django-nose/django-nose.png https://coveralls.io/repos/django-nose/django-nose/badge.svg?branch=master

django-nose provides all the goodness of nose in your Django tests, like:

  • Testing just your apps by default, not all the standard ones that happen to be in INSTALLED_APPS
  • Running the tests in one or more specific modules (or apps, or classes, or folders, or just running a specific test)
  • Obviating the need to import all your tests into tests/__init__.py. This not only saves busy-work but also eliminates the possibility of accidentally shadowing test classes.
  • Taking advantage of all the useful nose plugins

It also provides:

  • Fixture bundling, an optional feature which speeds up your fixture-based tests by a factor of 4
  • Reuse of previously created test DBs, cutting 10 seconds off startup time
  • Hygienic TransactionTestCases, which can save you a DB flush per test
  • Support for various databases. Tested with MySQL, PostgreSQL, and SQLite. Others should work as well.

django-nose requires nose 1.2.1 or later, and the latest release is recommended. It follows the Django's support policy, supporting:

  • Django 1.4 (LTS) with Python 2.6 and 2.7
  • Django 1.7 with Python 2.7 or 3.4
  • Django 1.8 (LTS) with Python 2.7 or 3.4

Development

Code:https://github.com/django-nose/django-nose
Issues:https://github.com/django-nose/django-nose/issues?state=open
Docs:https://django-nose.readthedocs.org
Something went wrong with that request. Please try again.