Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
C
cpython
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
0
Merge Requests
0
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
Kirill Smelkov
cpython
Commits
265281ac
Commit
265281ac
authored
Mar 27, 2013
by
Ezio Melotti
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
#17329: document unittest.SkipTest. Initial patch by Zachary Ware.
parent
7380a672
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
11 additions
and
4 deletions
+11
-4
Doc/library/unittest.rst
Doc/library/unittest.rst
+10
-3
Lib/unittest/case.py
Lib/unittest/case.py
+1
-1
No files found.
Doc/library/unittest.rst
View file @
265281ac
...
...
@@ -663,7 +663,7 @@ the test unless the passed object has a certain attribute::
def skipUnlessHasattr(obj, attr):
if hasattr(obj, attr):
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:
...
...
@@ -685,6 +685,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
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 classes will not have :meth:`setUpClass` or :meth:`tearDownClass` run.
...
...
@@ -2105,7 +2112,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
are not run and the ``tearDownClass`` is not run. Skipped classes will not
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.
...
...
@@ -2122,7 +2129,7 @@ These should be implemented as functions::
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
``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.
...
...
Lib/unittest/case.py
View file @
265281ac
...
...
@@ -23,7 +23,7 @@ class SkipTest(Exception):
"""
Raise this exception in a test to skip it.
Usually you can use Test
Result.skip
() or one of the skipping decorators
Usually you can use Test
Case.skipTest
() or one of the skipping decorators
instead of raising this directly.
"""
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment