stdout in Junit.xml

[yoram-s]

Thanks for submitting an issue!

Here's a quick checklist in what to include:

• Include a detailed description of the bug or suggestion
  With the following command lines:

pytest -s --junit-xml=junit.xml
pytest --junit-xml=junit.xml

The first junit file does not include the stdout in the junit xml.

We are running the pytest via jenkins on remote hardware. As we need to telnet the device and execute the steps remotely we are using pexepct to automate the remote execution.
On the one hand we need the junit xml file to display the result in jenkins, on the other hand we need the stdout to monitor the execution progress while running it with pexpect.
When test fails, we would like to get the associated stdout in the jenkins Junit report. Currently it is impossible

• pip list of the virtual environment you are using

alabaster (0.7.9)
ansi2html (1.2.0)
apipkg (1.4)
Arpeggio (1.5)
asserts (0.6)
astroid (1.5.2)
astunparse (1.5.0)
atomicwrites (1.1.5)
attrs (18.1.0)
autopep8 (1.3.1)
Babel (2.3.4)
baseconvert (1.0.0a4)
BitVector (3.4.7)
boto (2.28.0)
certifi (2018.10.15)
cffi (1.11.2)
chardet (3.0.4)
clang (5.0)
colorama (0.3.9)
configparser (3.5.0)
coverage (4.3.4)
CppHeaderParser (2.7.4)
cycler (0.10.0)
decorator (4.0.11)
Deprecated (1.2.4)
Django (1.11.6)
docutils (0.13.1)
execnet (1.5.0)
filelock (2.0.7)
flake8 (3.3.0)
flake8-polyfill (1.0.1)
future (0.17.1)
gcovr (3.4)
graphviz (0.8)
idna (2.7)
image (1.5.16)
imagesize (0.7.1)
ipdb (0.10.3)
ipykernel (4.6.1)
ipython (6.0.0)
ipython-genutils (0.2.0)
isodate (0.5.4)
isort (4.2.5)
jedi (0.10.2)
Jinja2 (2.9.4)
jsonschema (2.6.0)
junitparser (1.2.2)
jupyter-client (5.0.1)
jupyter-console (5.1.0)
jupyter-core (4.3.0)
lazy-object-proxy (1.2.2)
libclang-py3 (3.9.0)
llvmcpy (0.1.1)
lxml (3.7.2)
mando (0.6.4)
MarkupSafe (0.23)
mccabe (0.6.1)
more-itertools (4.2.0)
multipledispatch (0.4.9)
mypy (0.501)
mypy-lang (0.4.6)
nbformat (4.4.0)
netaddr (0.7.19)
nose (1.3.7)
numpy (1.13.0)
olefile (0.44)
ortools-examples (4.3.3802)
pandas (0.21.0)
pathlib (1.0.1)
pep8 (1.7.0)
pexpect (4.2.1)
pickleshare (0.7.4)
Pillow (4.3.0)
pip (9.0.1)
pluggy (0.6.0)
ply (3.10)
prompt-toolkit (1.0.14)
protobuf (3.0.0)
ptyprocess (0.5.1)
pudb (2018.1)
py (1.5.3)
py3-ortools (5.1.4041)
pyaml (16.12.2)
pycodestyle (2.3.1)
pycparser (2.18)
pydot (1.2.3)
pyeda (0.28.0)
pyexpect (1.0.17)
pyflakes (1.5.0)
PyGithub (1.43.3)
Pygments (2.2.0)
pygraphviz (1.3.1)
PyJWT (1.6.4)
pylint (1.7.1)
pyminifier (2.1)
Pympler (0.5)
pyparsing (2.2.0)
pytest (3.6.0)
pytest-doc (0.0.1)
pytest-forked (0.2)
pytest-leaks (0.2.2)
pytest-pudb (0.6)
pytest-repeat (0.7.0)
pytest-xdist (1.22.2)
python-bidi (0.4.0)
python-dateutil (2.6.0)
pytz (2016.10)
PyYAML (3.12)
pyzmq (16.0.2)
radon (2.0.2)
rdflib (4.2.2)
requests (2.20.1)
restclient (0.11.0)
rtl (0.4.3)
scapy-python3 (0.20)
scipy (1.0.0)
seaborn (0.8.1)
setuptools (28.8.0)
simplegeneric (0.8.1)
six (1.10.0)
snowballstemmer (1.2.1)
Sphinx (1.5.2)
sphinx-autodoc-annotation (1.0.post1)
sphinx-rtd-theme (0.3.0)
sphinxcontrib-fulltoc (1.1)
terminaltables (3.1.0)
testfixtures (4.13.3)
tornado (4.5.1)
traitlets (4.3.2)
typed-ast (1.0.2)
typing (3.5.3.0)
urllib3 (1.24.1)
urwid (2.0.1)
wcwidth (0.1.7)
wheel (0.29.0)
wrapt (1.10.10)
xml2json (1.1)
yapf (0.15.1)
z3-solver (4.5.1.0.post2)

• pytest and operating system versions
• Minimal example if possible

[RonnyPfannschmidt]

thats as intended -s disables the capture functionality which means we cant put anything since we cant capture anything

[csm10495]

@RonnyPfannschmidt , this would be really useful. I mean I can sort of hack it by doing something like this:

class TeeOutput():
    def __init__(self, outputs):
        self.outputs = outputs
    
    def write(self, msg):
        for i in self.outputs:
            i.write(msg)
        
    def flush(self):
        for i in self.outputs:
            i.flush()
            
def setupLogging():
    sys.stdout = TeeOutput([sys.__stdout__, sys.stdout])
    sys.stderr = TeeOutput([sys.__stderr__, sys.stderr])

then calling setupLogging() or maybe setting it up as some sort of fixture (haven't tried the fixture yet but who knows.). With this type of thing, without doing -s gives us output in both the junitxml and console.

I think the point is that we know what -s does but we're requesting a way to do this multi-output. Whether it uses -s or not is a different story.

[RonnyPfannschmidt]

Please log an issue abiut creating a new capture method