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

Migrate from nose to a different unittest provider #600

Open
bpblanken opened this issue Oct 26, 2023 · 2 comments
Open

Migrate from nose to a different unittest provider #600

bpblanken opened this issue Oct 26, 2023 · 2 comments
Assignees

Comments

@bpblanken
Copy link
Collaborator

the new v03 pipeline is using nose because that's what the v02 pipeline was using. However, it's not being maintained:

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](https://github.com/nose-devs/nose2), [py.test](http://pytest.org/), or just plain unittest/unittest2.

and fell over itself when pushing to python 3.10.

I've historically used py.test but a discussion and/or evaluation of other options is probably warranted.

@jklugherz
Copy link
Contributor

I've been writing a lot of new nose tests lately and am very interested in migrating to pytest!

@bpblanken
Copy link
Collaborator Author

yours if you'd like it!

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

No branches or pull requests

2 participants