junit xml results

[pytestbot]

Originally reported by: BitBucket: anomt, GitHub: anomt

---

I thought it would be nicer and better for long-running tests that the junit results won't be written only at the end of the entire test run, but after each test finishes.

I made the changes in
https://bitbucket.org/anomt/pytest-hacks

hope it'll be okay and to get your feedback

---

• Bitbucket: https://bitbucket.org/pytest-dev/pytest/issue/100

[pytestbot]

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

---

as far as i can tell, this patch will rewrite the entire junit output after every test

it would be interesting to change the behaviour from that to only rewriting the values in the header of the file
plus rewriting the tail of the file (replacing the by $nextresult

in order to make the changes in the head possible, something like non-significant whitespace can be used to "preallocate" the bytes that will later filled by more digits

however please wait with those experiments till holger gives a comment

[pytestbot]

Original comment by holger krekel (BitBucket: hpk42, GitHub: hpk42):

---

Is there anything apart form "I thought it was nicer" that motivated you to go for streaming XML?
Note that the resultlog plugin and --resultlog=PATH option provides streaming of test progress.
I am closing the issue until some concrete use cases pops up, e.g. a real-life consumer of streaming XML junit data.

[pytestbot]

Original comment by BitBucket: anomt, GitHub: anomt:

---

The problematic use-case was very long tests that run from a ci server that gets aborted in the middle because of a job timeout, the job gets aborted, no junitxml is found (it is written only at the end of a test run), and no results are shown.

I'd like to hear any suggestions.

[pytestbot]

Original comment by holger krekel (BitBucket: hpk42, GitHub: hpk42):

---

do you have a traceback from the aborted process and/or can send the console output? Maybe we get a chance to write out the junitxml before the process goes away.

[pytestbot]

Original comment by BitBucket: anomt, GitHub: anomt:

---

Nothing fancy happens, I am using Jenkins as the CI server.

This is a poc Jenkins build, it has two tests, first one succeeds immediately, the second one waits for a long time.
I abort the build, and the xml file is not written.
{{{

• py.test --junitxml=a.xml
  ============================= test session starts ==============================
  platform linux2 -- Python 2.7.1 -- pytest-2.2.2.dev2
  collecting ... collected 2 items

test_module.py .Build was aborted
Recording test results
No test report files were found. Configuration error?
Finished: ABORTED

}}}

[pytestbot]

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

---

doing this with junitxml itself is a bit fragile and messy

better solutions would be using a streaming format like subunit or xdist/boxed

there are some WIP there