I'd like to consider the idea of migrating the test set of all the python modules to pytest
It would help for several aspects, especially via the test fixtures mechanism, like make it easier to write tests for things like celery tasks (see celery fixtures for example)
The main problem is that it will most probably require to migrate all tests at once, which seems quite a job.
Update: we've decided to go ahead with this
I've submitted D516 as a showcase of a testsuite migration that would allow running pytest on swh.core
nice regexp-fu. We just have to make sure "grep 'istest'" doesn't return anything afterward
All tests in our unittest.TestCases are now named test_$something, which allows them to be picked up by pytest.
I've added a few missing tests/__init__.py files as well.
Running python3 -m pytest in all repositories seems to do a thing. In most cases the thing is even correct, and the tests are running (and successful).
The last nose-specific feature we're using is the @attr decorator, that is being used to mark tests that require a database, or stuff from swh-storage-testdata (so that they can be skipped, f.e. when building Debian packages). This can likely be replaced with a pytest mark instead.
(i've retitled this according to consensus)
adding another todo list item for completing this: Makefile.python in swh-environment should be migrated from nose to pytest