1. 8faa207 Issue #10979. unittest stdout buffering now works for class and module fixtures. by Michael Foord · 14 years ago
  2. 5657ff8 Improvement to fix for issue 9926 to allow TestResult to be reused. by Michael Foord · 14 years ago
  3. e5dc24e Merged revisions 86101 via svnmerge from by Michael Foord · 15 years ago
  4. 33958b8 Fix issue with nested test suites debug method and module setups. (unittest) by Michael Foord · 15 years ago
  5. 0fedb28 Issue 8948. cleanup functions are not run by unittest.TestCase.debug(), plus class and module teardowns are not run by unittest.TestSuite.debug(). by Michael Foord · 15 years ago
  6. db919f0 Tests for issue 8302, skipped test in a setUpClass or a setUpModule are reported as skips rather than errors. by Michael Foord · 15 years ago
  7. 20e287c Issue 8302. SkipTest exception is setUpClass or setUpModule is now reported as a skip rather than an error. by Michael Foord · 15 years ago
  8. 9c164af unittest: issue 8301. Adding functions to test suites no longer crashes. by Michael Foord · 15 years ago
  9. b1aa30f Issue 7815. __unittest in module globals trims frames from reported stacktraces in unittest. by Michael Foord · 15 years ago
  10. 5ffa325 Addition of setUpClass and setUpModule shared fixtures to unittest. by Michael Foord · 15 years ago
  11. b5d7400 Change error report when the object passed to suite.addTest is not by R. David Murray · 15 years ago
  12. e91ea56 Test discovery in unittest will only attempt to import modules that are importable; i.e. their names are valid Python identifiers. If an import fails during discovery this will be recorded as an error and test discovery will continue. Issue 6568. by Michael Foord · 16 years ago
  13. d7b0eeb split unittest.py into a package by Benjamin Peterson · 16 years ago