Metadata-Version: 2.0
Name: pytest-django
Version: 2.6.1
Summary: A Django plugin for py.test.
Home-page: http://pytest-django.readthedocs.org/
Author: Andreas Pelme
Author-email: andreas@pelme.se
License: UNKNOWN
Platform: UNKNOWN
Classifier: Development Status :: 5 - Production/Stable
Classifier: Framework :: Django
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: BSD License
Classifier: Operating System :: OS Independent
Classifier: Programming Language :: Python
Classifier: Topic :: Software Development :: Testing
Classifier: Programming Language :: Python :: 2.5
Classifier: Programming Language :: Python :: 2.6
Classifier: Programming Language :: Python :: 2.7
Classifier: Programming Language :: Python :: 3.2
Classifier: Programming Language :: Python :: 3.3
Requires-Dist: pytest (>=2.3.4)

.. image:: https://secure.travis-ci.org/pelme/pytest_django.png?branch=master
   :alt: Build Status
   :target: https://travis-ci.org/pelme/pytest_django

pytest-django is a plugin for `pytest <http://pytest.org/>`_ that provides a set of useful tools for testing `Django <http://www.djangoproject.com/>`_ applications and projects.

* Authors: Ben Firshman, Andreas Pelme and `contributors <https://github.com/pelme/pytest_django/contributors>`_
* Licence: BSD
* Compatibility: Django 1.3-1.7 (Django master is compatible at the time of each release), python 2.5-2.7, 3.2-3.3 or PyPy, pytest >= 2.3.4
* Project URL: https://github.com/pelme/pytest_django
* Documentation: http://pytest-django.rtfd.org/


Quick Start
===========
1. ``pip install pytest-django``
2. Make sure ``DJANGO_SETTINGS_MODULE`` is defined and and run tests with the ``py.test`` command.
3. (Optionally) If you put your tests under a tests directory (the standard Django application layout), and your files are not named ``test_FOO.py``, `see the FAQ <http://pytest-django.readthedocs.org/en/latest/faq.html#my-tests-are-not-being-picked-up-when-i-run-pytest-from-the-root-directory-why-not>`_


Documentation
==============

`Documentation is available on Read the Docs. <http://pytest-django.readthedocs.org/en/latest/index.html>`_


Why would I use this instead of Django's manage.py test command?
================================================================

Running the test suite with pytest offers some features that are not present in Djangos standard test mechanism:

 * Less boilerplate: no need to import unittest, create a subclass with methods. Just write tests as regular functions.
 * `Manage test dependencies with fixtures <http://pytest.org/latest/fixture.html>`_
 * Database re-use: no need to re-create the test database for every test run.
 * Run tests in multiple processes for increased speed
 * There are a lot of other nice plugins available for pytest.
 * Easy switching: Existing unittest-style tests will still work without any modifications.

See the `pytest documentation <http://pytest.org/latest/>`_ for more information on pytest.


Contributing
============

Read the `contributing page <http://pytest-django.readthedocs.org/en/latest/contributing.html>`_ from the documentation.

To run the project's tests::

    make test

To build the project's docs::

    make docs


Bugs? Feature suggestions?
============================

Report issues and feature requests at the `github issue tracker <http://github.com/pelme/pytest_django/issues>`_.


