setUpModule and tearDownModule in `__init__.py` not called by unittest

[pratt-fds]

Bug report

Bug description:

When structuring unittest tests across multiple files in a complex directory structure, module level setup and teardown functions, as described in the unittest documentation, are not called by the unittest framework. Running the same tests using pytest as the runner causes the setup and teardown functions to behave as expected.

File structure:

tests/
├── __init__.py
├── bar
│   ├── __init__.py
│   └── test_bar.py
├── base_class.py
└── foo
    ├── __init__.py
    └── test_foo.py

# tests/__init__.py content
def setUpModule():
    print("Setting up the tests module")

def tearDownModule():
    print("Tearing down the tests module")

# tests/base_class.py content
import unittest

class BaseTestCase(unittest.TestCase):
    @classmethod
    def setUpClass(cls):
        super().setUpClass()
        print("Setting up class resources in BaseTestCase")

    @classmethod
    def tearDownClass(cls):
        print("Tearing down class resources in BaseTestCase")
        super().tearDownClass()

# tests/foo/__init__.py content
def setUpModule():
    print("Setting up the tests.foo module")

def tearDownModule():
    print("Tearing down the tests.foo module")

# tests/foo/test_foo.py content
from tests.base_class import BaseTestCase

class FooTests(BaseTestCase):
    def test_foo(self):
        self.assertTrue(True)

# tests/bar/__init__.py file is empty

# tests/bar/bar.py content
from tests.base_class import BaseTestCase

def setUpModule():
    print("Setting up the tests.bar module")

def tearDownModule():
    print("Tearing down the tests.bar module")

class BarTests(BaseTestCase):
    def test_bar(self):
        self.assertTrue(True)

Actual output when running using unittest:

Received test ids from temp file.
Setting up the tests.bar module
Setting up class resources in BaseTestCase
test_bar (tests.bar.test_bar.BarTests) ... ok
Tearing down class resources in BaseTestCase
Tearing down the tests.bar module
Setting up class resources in BaseTestCase
test_foo (tests.foo.test_foo.FooTests) ... ok
Tearing down class resources in BaseTestCase
----------------------------------------------------------------------
Ran 2 tests in 0.000s

OK

Expected output when running using unittest:

Received test ids from temp file.
Setting up the tests module
Setting up the tests.bar module
Setting up class resources in BaseTestCase
test_bar (tests.bar.test_bar.BarTests) ... ok
Tearing down class resources in BaseTestCase
Tearing down the tests.bar module
Setting up the tests.foo module
Setting up class resources in BaseTestCase
test_foo (unittest_class_based.foo.test_foo.FooTests) ... ok
Tearing down class resources in BaseTestCase
Tearing down the tests.foo module
Tearing down the tests module
----------------------------------------------------------------------
Ran 2 tests in 0.000s

OK

CPython versions tested on:

3.10

Operating systems tested on:

Linux

[picnixz]

This may be tricky but I think it's because test files that are not prefixed by test_ are not discovered (see https://docs.python.org/3/library/unittest.html#unittest.TestLoader.discover). Can you check changing the name of a file (say test_bar to my_test_bar.py) and see if it the setUpModule/tearDownModule are called?

[picnixz]

I checked and yes, the issue is because test patterns really skip the content of __init__.py. Whatever tests you put in __init__.py won't be actually tested unless you add some load_tests functions & co + maybe a __main__ (see https://docs.python.org/3/library/unittest.html#load-tests-protocol).

I'm going to close this one as wont fix, sorry.