Skip to content

use pytest instead of nose for automated tests #204

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

Merged
merged 13 commits into from
Jul 5, 2016

Conversation

wholmgren
Copy link
Member

This PR switches pvlib from the nose testing framework to the pytest framework. I needed to learn pytest for another project, so pvlib is my pytest test. After a short learning curve, I've come to like Pytest a lot. Pytest seems much more powerful than nose. Also, nose is no longer maintained.

Another nice thing about pytest is that you can install the pytest-xdist plugin and run your tests in parallel across multiple cpu cores. My 4 core machine runs py.test pvlib in 46 seconds and py.test pvlib -n 4 in 19 seconds. This is more important for local testing since the CI builds are mostly limited by the bandwidth of those services.

I'll let this sit for a few days and then merge if there are no objections.

@wholmgren wholmgren added this to the 0.4.0 milestone Jun 27, 2016
@wholmgren wholmgren merged commit 55954bd into pvlib:master Jul 5, 2016
@wholmgren wholmgren deleted the pytest branch July 5, 2016 18:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant