In python, is there a good idiom for using context managers in setup/teardown

How about overriding unittest.TestCase.run() as illustrated below? This approach doesn't require calling any private methods or doing something to every method, which is what the questioner wanted.

from contextlib import contextmanagerimport unittest@contextmanagerdef resource_manager():    yield 'foo'class MyTest(unittest.TestCase):    def run(self, result=None):        with resource_manager() as resource:            self.resource = resource            super(MyTest, self).run(result)    def test(self):        self.assertEqual('foo', self.resource)unittest.main()

This approach also allows passing the TestCase instance to the context manager, if you want to modify the TestCase instance there.

Manipulating context managers in situations where you don't want a with statement to clean things up if all your resource acquisitions succeed is one of the use cases that contextlib.ExitStack() is designed to handle.

For example (using addCleanup() rather than a custom tearDown() implementation):

def setUp(self):    with contextlib.ExitStack() as stack:        self._resource = stack.enter_context(GetResource())        self.addCleanup(stack.pop_all().close)

That's the most robust approach, since it correctly handles acquisition of multiple resources:

def setUp(self):    with contextlib.ExitStack() as stack:        self._resource1 = stack.enter_context(GetResource())        self._resource2 = stack.enter_context(GetOtherResource())        self.addCleanup(stack.pop_all().close)

Here, if GetOtherResource() fails, the first resource will be cleaned up immediately by the with statement, while if it succeeds, the pop_all() call will postpone the cleanup until the registered cleanup function runs.

If you know you're only ever going to have one resource to manage, you can skip the with statement:

def setUp(self):    stack = contextlib.ExitStack()    self._resource = stack.enter_context(GetResource())    self.addCleanup(stack.close)

However, that's a bit more error prone, since if you add more resources to the stack without first switching to the with statement based version, successfully allocated resources may not get cleaned up promptly if later resource acquisitions fail.

You can also write something comparable using a custom tearDown() implementation by saving a reference to the resource stack on the test case:

def setUp(self):    with contextlib.ExitStack() as stack:        self._resource1 = stack.enter_context(GetResource())        self._resource2 = stack.enter_context(GetOtherResource())        self._resource_stack = stack.pop_all()def tearDown(self):    self._resource_stack.close()

Alternatively, you can also define a custom cleanup function that accesses the resource via a closure reference, avoiding the need to store any extra state on the test case purely for cleanup purposes:

def setUp(self):    with contextlib.ExitStack() as stack:        resource = stack.enter_context(GetResource())        def cleanup():            if necessary:                one_last_chance_to_use(resource)            stack.pop_all().close()        self.addCleanup(cleanup)

pytest fixtures are very close to your idea/style, and allow for exactly what you want:

import pytestfrom code.to.test import foo@pytest.fixture(...)def resource():    with your_context_manager as r:        yield rdef test_foo(resource):    assert foo(resource).bar() == 42