-
Notifications
You must be signed in to change notification settings - Fork 523
Update test runner to use pytest #495
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
Conversation
|
@jbrockmendel @mariocj89 I think this is fine, any comments? I'd like to merge ASAP so that everyone else can start using pytest. |
|
Looks great! I'd personally add a -vvvv for pytest to get the history of test run on the builds |
|
@mariocj89 Ah, good call, I didn't notice that that was missing. |
|
What is the difference between |
|
Just realized, it actually changes the way some diffs are reported. -v will add the test name in the reports. having multiple v just increases the level of verbosity, which adds extra information on some assertion failures. Example, if you assert two diffs which are different but big, adding extra verbosity will print the whole dict whilst just -v won't. |
|
OK, we can change it later if |
|
|
||
| script: | ||
| - coverage run --omit=setup.py,dateutil/test/* setup.py test | ||
| - coverage run --omit=setup.py,dateutil/test/* -m pytest -v |
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.
There is a pytest-cov plugin, not sure to what extent there is a "preferred" usage of that vs this usage.
|
Little late, but LGTM. |
This changes the test runner over to pytest.