Add Py.test testing framework support #6730
Conversation
|
Missed several other places, will update PR soon. |
|
Is this a continuation of #5325? |
|
Also, please be aware of https://github.com/matplotlib/pytest-mpl |
e8a4d60 to
32fc6b9
Compare
30bbacc to
0b30109
Compare
c3dc84e to
6931c9e
Compare
…test` `do_test` function variables are changed by loop where function was creates. It will work as you expect only if you call yielded function immediately.
745d683 to
391e981
Compare
|
Pytest 3.0 released with this change:
😕 |
The bug will not be fixed in pytest because generator functions are deprecated since pytest 3.0 release.
|
Coverage problem is because of |
|
PR is now ready for review and merge. Key notes:
|
|
It looks like pytest is finding 5 more tests than nose so that is probably a victory. It looks like pep8 is being run by pytest on travis, but not on appveyor, but that is ok for now. There is a big CI hit time wise for this and we will have to (soon) pick some of the nose builds to drop. |
I made this intentionally because we have separated pep8 only build on travis so there is no need to run them on all appveyor builds. Or I was wrong? |
|
If anything pep8 should be skipped by travis pytest build. According to the handy output, it is only 45s which is not a big deal on top of our total runtime. |
|
As far as I remember the main reason for splitting pep8 out in a separate build is not so much runtime but making it simpler to spot failures that are due to pep8 only |
This PR is part of preparation for migration to
pytest