Go to file
Floris Bruynooghe c93fbb0e57 Load conftest files in the correct order initially
When the conftest.py files are looked for intially they got loaded
starting from the subdir ending at the parent dir(s).  Later on during
collection any conftest.py files are loaded starting from the parent
dir ending at the subdir.  Due to how extending fixtures works the
latter is correct as otherwise the wrong fixture will be available.
So this changes the initial conftest loading to start at the root and
go towards the subdir.

This does also affect the order of other hooks, hence the order of the
reporting being different in testing/test_terminal.py.
2013-04-18 12:24:53 +01:00
_pytest Load conftest files in the correct order initially 2013-04-18 12:24:53 +01:00
bench python3 fixes 2010-11-23 20:32:07 -06:00
doc fix reference 2013-04-04 14:36:44 +02:00
testing Load conftest files in the correct order initially 2013-04-18 12:24:53 +01:00
.hgignore many doc improvements and fixes 2012-10-18 12:24:50 +02:00
.hgtags Added tag 2.3.4 for changeset ef299e57f242 2012-11-20 14:09:40 +01:00
AUTHORS added changelog entry for getfixture() for doctests 2013-03-21 12:41:39 +01:00
CHANGELOG add to changelog: put captured stdout/stderr into junitxml output even 2013-04-16 09:14:47 +02:00
ISSUES.txt add some bits to ISSUES 2013-01-27 02:10:29 +01:00
LICENSE * use the MIT license for the py lib 2009-10-03 01:11:04 +02:00
MANIFEST.in reanme README.txt to README.rst 2012-11-20 14:37:39 +01:00
README.rst reanme README.txt to README.rst 2012-11-20 14:37:39 +01:00
distribute_setup.py upgrade inlined distribute_setup.py 2012-05-22 17:24:43 +02:00
pytest.py avoid double-instantiation of PluginManager in case of the "python pytest.py" or -m pytest invocation 2012-09-25 11:58:41 +02:00
setup.py - add release announce 2013-03-28 10:21:03 +01:00
tox.ini - add release announce 2013-03-28 10:21:03 +01:00

README.rst

The ``py.test`` testing tool makes it easy to write small tests, yet
scales to support complex functional testing.  It provides

- `auto-discovery
  <http://pytest.org/latest/goodpractises.html#python-test-discovery>`_
  of test modules and functions,
- detailed info on failing `assert statements <http://pytest.org/latest/assert.html>`_ (no need to remember ``self.assert*`` names)
- `modular fixtures <http://pytest.org/latest/fixture.html>`_  for
  managing small or parametrized long-lived test resources.
- multi-paradigm support: you can use ``py.test`` to run test suites based
  on `unittest <http://pytest.org/latest/unittest.html>`_ (or trial),
  `nose <http://pytest.org/latest/nose.html>`_
- single-source compatibility to Python2.4 all the way up to Python3.3,
  PyPy-1.9 and Jython-2.5.1.

- many `external plugins <http://pytest.org/latest/plugins.html#installing-external-plugins-searching>`_.

A simple example for a test::

    # content of test_module.py
    def test_function():
        i = 4
        assert i == 3

which can be run with ``py.test test_module.py``.  See `getting-started <http://pytest.org/latest/getting-started.html#our-first-test-run>`_ for more examples.

For much more info, including PDF docs, see

    http://pytest.org

and report bugs at:

    http://bitbucket.org/hpk42/pytest/issues/

Copyright Holger Krekel and others, 2004-2012