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

Switch to pytest? #327

Closed
dargueta opened this issue Jul 30, 2019 · 5 comments · Fixed by #337
Closed

Switch to pytest? #327

dargueta opened this issue Jul 30, 2019 · 5 comments · Fixed by #337
Assignees

Comments

@dargueta
Copy link
Contributor

nose is no longer maintained (last release was in 2015) so I think we should consider moving on to a different testing framework. pytest gets us a lot of things like simplified argument parametrization and a lot of plugins we can install. It works with unittest so I don't think the move will require an overhaul.

@lurch
Copy link
Contributor

lurch commented Jul 30, 2019

@willmcgugan
Copy link
Member

Yeah, pytest seems to be the dominant framework these days. I use it in other projects. I'm not sure what's involved in switching, hope I don't have to individually edit the tests.

@willmcgugan willmcgugan self-assigned this Aug 3, 2019
@dargueta
Copy link
Contributor Author

dargueta commented Aug 5, 2019

hope I don't have to individually edit the tests.

Aside from removing references to nose-specific stuff, no. I'll have a PR soon.

@dargueta dargueta mentioned this issue Aug 6, 2019
9 tasks
@dargueta
Copy link
Contributor Author

dargueta commented Aug 6, 2019

Working on it in #337, may need help fixing Appveyor since I've never used it before and don't really know what I'm doing.

@dargueta
Copy link
Contributor Author

dargueta commented Aug 8, 2019

I added a plugin to randomize test execution order and it looks like we have some hidden test interdependencies I can't figure out. Help would be most welcome.

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

Successfully merging a pull request may close this issue.

3 participants