| 
								
								
									 Michael Foord | 0fedb28951 | Issue 8948. cleanup functions are not run by unittest.TestCase.debug(), plus class and module teardowns are not run by unittest.TestSuite.debug(). | 2010-06-08 22:44:52 +00:00 |  | 
				
					
						| 
								
								
									 Michael Foord | db919f0188 | Tests for issue 8302, skipped test in a setUpClass or a setUpModule are reported as skips rather than errors. | 2010-06-05 20:59:00 +00:00 |  | 
				
					
						| 
								
								
									 Michael Foord | 20e287caed | Issue 8302. SkipTest exception is setUpClass or setUpModule is now reported as a skip rather than an error. | 2010-06-05 19:38:42 +00:00 |  | 
				
					
						| 
								
								
									 Michael Foord | 9c164af6c3 | unittest: issue 8301. Adding functions to test suites no longer crashes. | 2010-05-08 17:06:25 +00:00 |  | 
				
					
						| 
								
								
									 Michael Foord | b1aa30f94d | Issue 7815. __unittest in module globals trims frames from reported stacktraces in unittest. | 2010-03-22 00:06:30 +00:00 |  | 
				
					
						| 
								
								
									 Michael Foord | 5ffa325a82 | Addition of setUpClass and setUpModule shared fixtures to unittest. | 2010-03-07 22:04:55 +00:00 |  | 
				
					
						| 
								
								
									 R. David Murray | b5d7400e8a | Change error report when the object passed to suite.addTest is not callable to include the repr of the invalid object. | 2010-01-28 21:16:33 +00:00 |  | 
				
					
						| 
								
								
									 Michael Foord | e91ea56b30 | 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. | 2009-09-13 19:07:03 +00:00 |  | 
				
					
						| 
								
								
									 Benjamin Peterson | d7b0eebcae | split unittest.py into a package | 2009-07-19 20:18:21 +00:00 |  |