id,summary,reporter,owner,description,type,status,component,version,severity,resolution,keywords,cc,stage,has_patch,needs_docs,needs_tests,needs_better_patch,easy,ui_ux 18417,override_settings doesn't work with unittest.TestCase subclasses,Claude Paroz,nobody,"Currently, if you decorate with override_settings a subclass of unittest.!TestCase, all tests in the class are silently skipped. This is happening because of the issubclass(!TransactionTestCase) test here: https://github.com/django/django/blob/master/django/test/utils.py#L188 We cannot simply change the issubclass test, because ut.!TestCase doesn't have any _pre_setup mechanism. I can see two ways forward: * Document that override_settings cannot decorate unittest.!TestClass subclasses, and raise an error when the decorator is applied to anything other than !TransactionTestCase subclasses. * Instead of using _pre_setup, use setUpClass to enable the overriden settings. I'd really like to see the second alternative implemented. However, this means that the override_settings machinery will only run at the start of the !TestClass tests, and no more between each test (unless the specific test itself is decorated by override_settings). This shouldn't disturb the test system more than that.",Bug,closed,Testing framework,1.4,Normal,fixed,,asendecka@…,Design decision needed,1,0,0,0,0,0