Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider switching to py.test #588

Closed
audiodude opened this issue Mar 17, 2023 · 0 comments · Fixed by #670
Closed

Consider switching to py.test #588

audiodude opened this issue Mar 17, 2023 · 0 comments · Fixed by #670

Comments

@audiodude
Copy link
Member

Nose (nosetests), which we use as our test harness/test runner, has the following note on its docs page:

Note to Users
Nose has been in maintenance mode for the past several years and will likely cease without a new person/team to take over maintainership. New projects should consider using Nose2, py.test, or just plain unittest/unittest2.

We should switch to py.test. It shouldn't be so hard, since we're not using any nose specific features besides automatic test collection, which I believe py.test has as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant