-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Use pytest instead of unittest #2446
Copy link
Copy link
Closed
Labels
internalscomponent : psutil's own machinery, incl. debug output. No effect on the public APIcomponent : psutil's own machinery, incl. debug output. No effect on the public APItestscomponent : tests/ - the suite itself, not a bug it happens to catchcomponent : tests/ - the suite itself, not a bug it happens to catch
Description
Metadata
Metadata
Assignees
Labels
internalscomponent : psutil's own machinery, incl. debug output. No effect on the public APIcomponent : psutil's own machinery, incl. debug output. No effect on the public APItestscomponent : tests/ - the suite itself, not a bug it happens to catchcomponent : tests/ - the suite itself, not a bug it happens to catch
I recently did this for pyftpdlib giampaolo/pyftpdlib#628.
Reasons:
self.assert*APIs (easier to read, shorter to type)assertstatements #2453pytest-xdistextension allows for parallel test execution, so we can get rid of our internal implementation (less code to maintain) - DONE in Use pytest, get rid of test/runner.py #2447pytestmay not be installed, we still want to be able to test psutil installation viapython3 -m psutil.testsby usingunittesttest runner - DONE in Run tests without pytests #2456.