Metadata-Version: 1.0
Name: pytest-django
Version: 1.3.2
Summary: A Django plugin for py.test.
Home-page: http://pytest-django.readthedocs.org/
Author: Andreas Pelme
Author-email: andreas@pelme.se
License: UNKNOWN
Description: pytest-django is a plugin for `py.test <http://pytest.org/>`_ that provides a set of useful tools for testing `Django <http://www.djangoproject.com/>`_ applications and projects.
        
        Requirements
        ============
        
        These packages are required to use pytest-django, and should be installed
        separately.
        
         * Django 1.3+ (1.4 is supported)
        
         * py.test
        
        
        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-py-test-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 py.test offers some features that are not present in Djangos standard test mechanism:
        
         * `Smarter test discovery <http://pytest.org/latest/example/pythoncollection.html>`_ (no need for ``from .foo import *`` in your test modules).
         * Less boilerplate: no need to import unittest, create a subclass with methods. Just write tests as regular functions.
         * `Injection of test depencies with funcargs <http://pytest.org/latest/funcargs.html>`_
         * No need to run all tests, `it is easy to specify which tests to run <http://pytest.org/latest/usage.html#specifying-tests-selecting-tests>`_.
         * Database re-use: no need to re-create the test database for every test run.
         * No hacks required to only run your apps, and not the 3rd party/contrib apps that is listed in your ``INSTALLED_APPS``.
         * There are a lot of other nice plugins available for py.test.
         * No pain of switching: Existing unittest-style tests will still work without any modifications.
        
        See the `py.test documentation <http://pytest.org/latest/>`_ for more information on py.test.
        
        
        Bugs? Feature suggestions?
        ============================
        Report issues and feature requests at the `github issue tracker <http://github.com/pelme/pytest_django/issues>`_.
        
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
