Skip to content

Show stdout and stderr of passed tests #125

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.

Sign up for GitHub

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

Jump to bottom
Closed
pytestbot opened this issue Feb 17, 2012 · 2 comments
Closed

Show stdout and stderr of passed tests #125

pytestbot opened this issue Feb 17, 2012 · 2 comments
Labels
type: proposal proposal for a new feature, often to gather opinions or design the API around the new feature

Comments

@pytestbot
Copy link
Contributor

Originally reported by: Dmitry Panin (BitBucket: pankdm, GitHub: pankdm)

According to documentation: "During test execution any output sent to stdout and stderr is captured. If a test or a setup method fails its according captured output will usually be shown along with the failure traceback."

But I haven't found the way to watch output of passed tests. Does py.test have such possibility (option passed via commandline will be great)?
@pytestbot
Copy link
Contributor Author

Original comment by Ronny Pfannschmidt (BitBucket: RonnyPfannschmidt, GitHub: RonnyPfannschmidt):

you can disable output capturing with the -s flag

there is no option for special reporting of the stdio of passed tests

i suppose something similar to the output in failure might be helpful?

@pytestbot
Copy link
Contributor Author

Original comment by Dmitry Panin (BitBucket: pankdm, GitHub: pankdm):

Thanks a lot! Flag -s worked fine.
Actually there was a bug in my program so I didn't get output.

@pytestbot pytestbot added the type: proposal proposal for a new feature, often to gather opinions or design the API around the new feature label Jun 15, 2015
fkohlgrueber pushed a commit to fkohlgrueber/pytest that referenced this issue Oct 27, 2018
@zsol @ambv
Support parsing of async generators in non-async functions (pytest-de…
8836893 
…v#165)

This is a new syntax added in python3.7, so black can't verify that reformatting will not change the ast unless black itself is run with 3.7. We'll need to change the error message black gives in this case. @ambv any ideas?

Fixes pytest-dev#125.
mgorny pushed a commit to mgorny/pytest that referenced this issue May 27, 2023
@jcfr
Add support for pytest 4.x and test against python 3.7
abffd67 
----
ci: Test against Python 3.7

----
ci: Skip Coveralls submission if COVERALLS_REPO_TOKEN env. var is empty

----
ci: Update circleci image to allow install of python 3.7
See https://circleci.com/docs/2.0/configuration-reference/#machine

----
pytest-server-fixture: Fix rethinkdb tests requiring rethinkdb < 2.4.0

The current implementation needs to be refactored to support the latest
release of rethinkdb-python package. See pytest-dev#132

----
wheels: Generate universal wheels installable with both python 2.x and 3.x
See pytest-dev#125

Fix DeprecationWarning warnings using "logger.warning()" function

----
pytest-virtualenv: Add virtualenv as install requirement. Fixes pytest-dev#122

Remove requirement for pytest<4.0.0
See pytest-dev#100

----
pytest-webdriver: Fix RemovedInPytest4Warning using getfixturevalue

This commit fixes the following error:

  >           root_uri.append(request.getfuncargvalue('pyramid_server').uri)
  E           RemovedInPytest4Warning: getfuncargvalue is deprecated, use getfixturevalue

  pytest_webdriver.py:62: RemovedInPytest4Warning

See pytest-dev#100

----
pytest-verbose-parametrize: Add support for revamped marker infrastructure

This commit fixes tests failing with pytest > 4.0.0

----
pytest-verbose-parametrize: Fix integration tests to support pytest >= 4.1.0

This commit updates tests to support version of pytest with
pytest-dev/pytest@e9b2475e2 (Display actual test ids in `--collect-only`)

----
dist: Remove support for building and distributing *.egg files

Wheel is currently considered the standard for built and binary
packaging for Python

See https://packaging.python.org/discussions/wheel-vs-egg/

See pytest-dev#125

----
VagrantFile: Install python 3.7 and initialize python 3.7 by default
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: proposal proposal for a new feature, often to gather opinions or design the API around the new feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@pytestbot