-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Proposal: Verbose output from tests through decorators. #1792
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
Comments
Another alternative is:
|
Just FYI in pytest-3.0 def test_bar(capsys):
with capsys.disabled():
bar()
print "bar called" |
Thanks 😄 I am on |
3.0 is not out yet (will be out probably next week), sorry for not being clearer. Also, I think your proposal is independent from the disabled() context manager and could be implemented as an alternative. 😁 |
Awesome 😃 |
I'm not sure if it's worth having yet another way™ to disable capturing in the core 😉 I guess if someone wants a marker like this, it'd probably be some 5-line hook in |
Pytest 3 has been released and I have the feature what I wished to. Thanks, closing this. 😄 |
Sometimes there are thousands of tests which may print too much on
stdout
orstderr
. In that case, we need verbose output from ten of the tests. To facilitate this, we may introduce a marker for not capturing the output for certain tests.Final mechanism can be as follows:
Captured outputs can roughly be depicted as:
py.test
py.test --capture=no
It may be taken up a step further to have verbose output from a module / directory recursion through
pytest.ini
support.The text was updated successfully, but these errors were encountered: