SF bug #1078905: Docs for unittest run() methods are misleading

This commit is contained in:
Raymond Hettinger 2004-12-04 21:21:53 +00:00
parent 46ea4c810f
commit 664347be94
2 changed files with 9 additions and 4 deletions

View File

@ -277,7 +277,8 @@ class TestCase:
finally:
result.stopTest(self)
__call__ = run
def __call__(self, *args, **kwds):
return self.run(*args, **kwds)
def debug(self):
"""Run the test without collecting errors in a TestResult"""
@ -417,15 +418,15 @@ class TestSuite:
self.addTest(test)
def run(self, result):
return self(result)
def __call__(self, result):
for test in self._tests:
if result.shouldStop:
break
test(result)
return result
def __call__(self, *args, **kwds):
return self.run(*args, **kwds)
def debug(self):
"""Run the tests without collecting errors in a TestResult"""
for test in self._tests: test.debug()

View File

@ -21,6 +21,10 @@ Extension Modules
Library
-------
- unittest.TestCase.run() and unittest.TestSuite.run() can now be successfully
extended or overridden by subclasses. Formerly, the subclassed method would
be ignored by the rest of the module. (Bug #1078905).
- the deprecated whrandom module was removed. Use the random module instead.
- heapq.nsmallest() and heapq.nlargest() now support key= arguments with