-
Notifications
You must be signed in to change notification settings - Fork 752
Migrate to Pytest #368
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 to Pytest #368
Conversation
Also another nice feature is that it has a nicer output
vs
|
Codecov Report
@@ Coverage Diff @@
## master #368 +/- ##
==========================================
+ Coverage 63.08% 63.18% +0.09%
==========================================
Files 61 61
Lines 5239 5239
Branches 876 876
==========================================
+ Hits 3305 3310 +5
+ Misses 1715 1709 -6
- Partials 219 220 +1
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a very good idea. We just need to fix the conda recipe, too.
MANIFEST.in
Outdated
@@ -0,0 +1,20 @@ | |||
graft docs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What is this file for?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I forgot to remove that commit/file. Its supposed to replace the _get_source_files
in setup.py
.
I didn't get around to testing it though. Removing it fixes the conda recipe.
Let me fix that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same question
@filmor @denfromufa conda recipe fixed. |
All builds finished, none of them had the conda.recipe build error from the manifest. Looks like we are good to merge then? |
I like the switch to pytest, can you give 1-2 days to review this and test locally? @vmuriart |
Sure. Test wise, nothing changed other than indent level. |
Even PyPy ;)
…On Wed, Feb 8, 2017, 8:38 PM Victor Uriarte ***@***.***> wrote:
Sure. Test wise, nothing changed other than indent level.
Have you tried using tox for testing? It will let you run against all
interpreters you have installed.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#368 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHgZ5X_DQ7KgYJQDZTxogIfb8MNoSmYdks5ranw7gaJpZM4L7OID>
.
|
You can configure it for it; though idk if pythonnet would have any issues w it. |
@denfromufa did you get a chance to finish testing? |
Sorry, PyPy got me distracted. Let me try pytest tonight. If not, then you
can merge tomorrow.
…On Mon, Feb 13, 2017, 8:39 AM Victor Uriarte ***@***.***> wrote:
@denfromufa <https://github.com/denfromufa> did you get a chance to
finish testing?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#368 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHgZ5d27xZjOSol_YidLnO0iIPy6bfFzks5rcGsYgaJpZM4L7OID>
.
|
pytest on travis initially required `sudo=required` otherwise failed. Without the sudo flag pytest wasn't being upgraded. Needed to force upgrade. pytest-dev/pytest#2240
Needs local imports to work. Conversion done with unittests2pytests and a couple regex
Control settings for some add-ons like pytest
What does this implement/fix? Explain your changes.
Unittests
module requires alot of boilerplate setup to get running.Pytest
the process of unittest writing within python making it easier for new contributors to add tests.Does this close any currently open issues?
N/A
Any other comments?
This was the original meant to be part of #329 but decided to separate it out.
Checklist
Check all those that are applicable and complete.
AUTHORS
CHANGELOG