Initializes shared test resources at the class level before any test methods execute.

Signals that the following block prepares shared state for a test suite.

When you need to set up expensive or shared resources (e.g., database connections, file handles) once per test class rather than per test.

Inside a unittest.TestCase subclass, typically placed at the top of the class definition before any test methods.

@classmethod\ndef setUpClass(cls):\n cls.shared = SharedResource()\n cls.shared.setup()

@classmethod def setUpClass(cls): cls.shared = <Resource>(); cls.shared.setup()

• unittest.TestCase
• test methods
• tearDownClass
• setUp
• tearDown

• Using setUp per test (more isolated but slower)
• using module-level setup with setUpModule (runs once per module)
• using pytest fixtures with scope='session' (more flexible reuse).

Forgot @classmethod decorator causing AttributeError on cls; used self instead of cls creating instance attribute instead of class attribute; forgot to call super().setUpClass() in subclass causing parent setup to be skipped; assumed shared resource resets between tests leading to state leakage.

setUp (runs before each test method); tearDownClass (cleans up after all tests); setUpModule (module-level setup once per module); pytest fixtures with scope='session' (flexible reusable setup).

Coming from JUnit: may use @BeforeClass instead of @classmethod def setUpClass(cls): — use @classmethod decorator and first argument cls.; Coming from pytest: may expect fixture with autouse instead of unittest style — use @classmethod setUpClass for class-level setup in unittest.

• setUp
• tearDown
• setUpClass
• tearDownClass
• setUpModule
• tearDownModule

Avoid using setUpClass for resources that vary per test or require isolation, as shared state can cause test interdependence; Sharing expensive resources reduces setup time but risks hidden coupling and difficult debugging if state leaks; Remember to call super().setUpClass() in subclasses to preserve parent setup, otherwise parent initialization may be skipped.

Using setUpClass ensures expensive setup runs once, speeding up test suites and providing consistent preconditions, which reduces flaky tests caused by inconsistent setup.

Think of setUpClass as the stage crew that builds the set once before the play begins, so every actor (test) can perform without rebuilding the set.

If the shared resource raises an exception during setup, the entire test class is skipped or marked as error, preventing any tests from running.

Use pytest fixtures with scope='session' for more flexible and reusable test setup.