fix issue377 by clarifying in the nose-compat docs that pytest

does not duplicate the unittest-API into the "plain" namespace.
This commit is contained in:
holger krekel 2013-11-22 14:07:56 +01:00
parent 40b172ca5a
commit 1dc2a45cb2
2 changed files with 13 additions and 1 deletions

View File

@ -82,6 +82,9 @@ Unreleased
- fixed version comparison in pytest.importskip(modname, minverstring)
- fix issue377 by clarifying in the nose-compat docs that pytest
does not duplicate the unittest-API into the "plain" namespace.
Changes between 2.4.1 and 2.4.2
-----------------------------------

View File

@ -30,9 +30,18 @@ Supported nose Idioms
Unsupported idioms / known issues
----------------------------------
- unittest-style ``setUp, tearDown, setUpClass, tearDownClass``
are recognized only on ``unittest.TestCase`` classes but not
on plain classes. ``nose`` supports these methods also on plain
classes but pytest deliberately does not. As nose and pytest already
both support ``setup_class, teardown_class, setup_method, teardown_method``
it doesn't seem useful to duplicate the unittest-API like nose does.
If you however rather think pytest should support the unittest-spelling on
plain classes please post `to this issue
<https://bitbucket.org/hpk42/pytest/issue/377/>`_.
- nose-style doctests are not collected and executed correctly,
also doctest fixtures don't work.
- no nose-configuration is recognized