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

Better report doubles.verify failures in pytest #131

Merged
merged 2 commits into from
Jun 7, 2018

Conversation

toddsifleet
Copy link
Contributor

* If doubles.verify finds unsatisfied expections, report the test as a
failure not an error.
@CLAassistant
Copy link

CLAassistant commented Apr 26, 2018

CLA assistant check
All committers have signed the CLA.

@coveralls
Copy link

coveralls commented Apr 26, 2018

Coverage Status

Coverage remained the same at 97.689% when pulling 9f35b40 on tws-better-report-expectation-failures into 96da534 on master.

test/conftest.py Outdated
from doubles.pytest_plugin import pytest_runtest_protocol # noqa
except ImportError:
from doubles.pytest_plugin import pytest_runtest_call # noqa
from doubles.pytest_plugin import pytest_pyfunc_call # noqa

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

for reusing plugin modules explicitly the recommended pattern is to set pytest_plugins = ['doubles.pytest_plugin'] instead of importing parts (this ensures the whole plugin gets used without having to track what to import)

@toddsifleet toddsifleet merged commit 0900dc9 into master Jun 7, 2018
@skudriashev skudriashev deleted the tws-better-report-expectation-failures branch July 30, 2018 20:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Doubles's pytest plugin reports failed assertion as errors rather than failed tests
4 participants