mirror of
https://github.com/python/cpython.git
synced 2025-09-26 18:29:57 +00:00
#17329: merge with 3.2.
This commit is contained in:
commit
184e59357e
2 changed files with 11 additions and 4 deletions
|
@ -530,7 +530,7 @@ the test unless the passed object has a certain attribute::
|
||||||
def skipUnlessHasattr(obj, attr):
|
def skipUnlessHasattr(obj, attr):
|
||||||
if hasattr(obj, attr):
|
if hasattr(obj, attr):
|
||||||
return lambda func: func
|
return lambda func: func
|
||||||
return unittest.skip("{0!r} doesn't have {1!r}".format(obj, attr))
|
return unittest.skip("{!r} doesn't have {!r}".format(obj, attr))
|
||||||
|
|
||||||
The following decorators implement test skipping and expected failures:
|
The following decorators implement test skipping and expected failures:
|
||||||
|
|
||||||
|
@ -552,6 +552,13 @@ The following decorators implement test skipping and expected failures:
|
||||||
Mark the test as an expected failure. If the test fails when run, the test
|
Mark the test as an expected failure. If the test fails when run, the test
|
||||||
is not counted as a failure.
|
is not counted as a failure.
|
||||||
|
|
||||||
|
.. exception:: SkipTest(reason)
|
||||||
|
|
||||||
|
This exception is raised to skip a test.
|
||||||
|
|
||||||
|
Usually you can use :meth:`TestCase.skipTest` or one of the skipping
|
||||||
|
decorators instead of raising this directly.
|
||||||
|
|
||||||
Skipped tests will not have :meth:`setUp` or :meth:`tearDown` run around them.
|
Skipped tests will not have :meth:`setUp` or :meth:`tearDown` run around them.
|
||||||
Skipped classes will not have :meth:`setUpClass` or :meth:`tearDownClass` run.
|
Skipped classes will not have :meth:`setUpClass` or :meth:`tearDownClass` run.
|
||||||
|
|
||||||
|
@ -1958,7 +1965,7 @@ then you must call up to them yourself. The implementations in
|
||||||
If an exception is raised during a ``setUpClass`` then the tests in the class
|
If an exception is raised during a ``setUpClass`` then the tests in the class
|
||||||
are not run and the ``tearDownClass`` is not run. Skipped classes will not
|
are not run and the ``tearDownClass`` is not run. Skipped classes will not
|
||||||
have ``setUpClass`` or ``tearDownClass`` run. If the exception is a
|
have ``setUpClass`` or ``tearDownClass`` run. If the exception is a
|
||||||
``SkipTest`` exception then the class will be reported as having been skipped
|
:exc:`SkipTest` exception then the class will be reported as having been skipped
|
||||||
instead of as an error.
|
instead of as an error.
|
||||||
|
|
||||||
|
|
||||||
|
@ -1975,7 +1982,7 @@ These should be implemented as functions::
|
||||||
|
|
||||||
If an exception is raised in a ``setUpModule`` then none of the tests in the
|
If an exception is raised in a ``setUpModule`` then none of the tests in the
|
||||||
module will be run and the ``tearDownModule`` will not be run. If the exception is a
|
module will be run and the ``tearDownModule`` will not be run. If the exception is a
|
||||||
``SkipTest`` exception then the module will be reported as having been skipped
|
:exc:`SkipTest` exception then the module will be reported as having been skipped
|
||||||
instead of as an error.
|
instead of as an error.
|
||||||
|
|
||||||
|
|
||||||
|
|
|
@ -22,7 +22,7 @@ class SkipTest(Exception):
|
||||||
"""
|
"""
|
||||||
Raise this exception in a test to skip it.
|
Raise this exception in a test to skip it.
|
||||||
|
|
||||||
Usually you can use TestResult.skip() or one of the skipping decorators
|
Usually you can use TestCase.skipTest() or one of the skipping decorators
|
||||||
instead of raising this directly.
|
instead of raising this directly.
|
||||||
"""
|
"""
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue