Converting From unittest to pytest#
Conversion Checklist#
Note
Please bear in mind the following checklist is for general use; there may be some cases which require extra context or thought before implementing these changes.
Before making any manual changes, run dannysepler/pytestify on the file. This does a lot of the brunt work for you!
Check for references to
IrisTest. If a class inherits from this, remove the inheritance. Inheritance is unnecessary for pytest tests, soiris.tests.IrisTesthas been deprecated and its convenience methods have been moved to theiris.tests._shared_utilsmodule.Check for references to
unittest. Many of the functions within unittest are also in pytest, so often you can just change where the function is imported from.Check for references to
self.assert. Pytest has a lighter-weight syntax for assertions, e.g.assert x == 2instead ofassertEqual(x, 2). In the case of customIrisTestassertions, the majority of these have been replicated iniris.tests._shared_utils, but with snake_case instead of camelCase. Someiris.tests.IrisTestassertions have not been converted intoiris.tests._shared_utils, as these were deemed easy to achieve via simpleassert ...statements.Check for references to
setup_method(). Replace this with_setup()instead. Ensure that this is decorated with@pytest.fixture(autouse=True).@pytest.fixture(autouse=True) def _setup(self): ...
Check for references to
super(). Most test classes used to inherit fromiris.tests.IrisTest, so references to this should be removed. Any inheritance patterns in_setup()(see above) can be achieved by ‘chaining’ fixtures; note that each setup fixture needs a unique name:class TestFoo: @pytest.fixture(autouse=True) def _setup_foo(self): ... class TestBar(TestFoo): @pytest.fixture(autouse=True) def _setup(self, _setup_foo): ...
Check for references to
@tests. These should be changed to@_shared_utils.Check for
mock.patch("warnings.warn"). This can be replaced withpytest.warns(match=message).Check for references to
mockorself.patch. These should be changed to use themockerfixture - see the pytest-mock docs. Note that pytest-mock’spatchdoes not support the context-manager syntax; in most cases this is made unnecessary (see Usage as context manager), in advanced cases consider using the monkeypatch fixture to provide a context-manager.Check for
np.testing.assert.... This can usually be swapped for_shared_utils.assert....Check for
np.allclose. This should be swapped for_shared_utils.assert_array_all_close.Check for references to
self.tmp_dirandself.temp_filename. In pytest,tmp_pathis used instead, and can be passed into functions as a fixture.Check for
if __name__ == 'main'. This is no longer needed with pytest.Remove the top-level import of
iris.tests(usuallyimport iris.tests as tests). Having followed the above steps, any remaining calls (e.g.iris.tests.get_data_path()) should be easily replacable with calls toiris.tests._shared_utils(e.g.iris.tests._shared_utils.get_data_path()).Ensure that all test classes start with
Test. Tests will not run in pytest without it.Check the file against astral-sh/ruff , using
pip install ruff->ruff check --select PT <file>.Ensure that all the tests are passing. Some tests are set to skip if certain packages aren’t installed in your environment. These are often also skipped in the Iris CI also, so make sure that they run and pass locally.
Common Translations#
|
|
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|