How can I remove library code calls from pytest traceback?
I'm using pytest with mock in my python project.
When I get a test failure that involves a mock object (almost all of
them), the traceback dives into the mock library source code and my code
that's actually triggering the failure often scrolls out of view.
Is there a way to tell py.test to exclude installed libraries from the
traceback or something like that? The noise level is taking away from what
is otherwise a sweet testing library.
No comments:
Post a Comment