I think this test should be in its own class so it can have a setUp/tearDown with the "old_warn_override_settings" logic. If the assertions fail, COMPLEX_OVERRIDE_SETTINGS won't be restored to its original values which would cause the test to leak state.