Karthikeyan Singaravelan <tir.kar...@gmail.com> added the comment:
In my test cases I have ended up just ignoring the mock object with a placeholder if it's not needed. For the given use case you can do this using patch objects at setUp and tearDown like in https://docs.python.org/dev/library/unittest.mock-examples.html#applying-the-same-patch-to-every-test-method . I feel introducing another argument increases the complexity on the existing patch api which already has a lot of options. I have added others for their thoughts on this API change. from unittest.mock import Mock, patch from unittest import TestCase, main class Foo: properties = [] class FooTest(TestCase): def setUp(self): patcher = patch(f"{__name__}.Foo.properties", new_callable=list) self.addCleanup(patcher.stop) patcher.start() def test_foo(self): Foo.properties.append(1) self.assertEqual(Foo.properties, [1]) def test_bar(self): Foo.properties.append(2) self.assertEqual(Foo.properties, [2]) if __name__ == "__main__": main() ---------- nosy: +cjw296, lisroach, mariocj89, michael.foord, xtreak type: -> behavior versions: +Python 3.11 _______________________________________ Python tracker <rep...@bugs.python.org> <https://bugs.python.org/issue44052> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: https://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
