A new flag would be fine for our use case (and wouldn't disrupt anyone else's dependence on the existing behavior).
Is this something that would be pretty easy to implement? How soon could it be available? On Tue, Jan 21, 2014, at 03:12 PM, Bruno Oliveira wrote: Same here. I think a better approach would be a new flag. Perhaps "--append-to-junitxml"? On Tue, Jan 21, 2014 at 8:46 PM, Jason R. Coombs <[1]jar...@jaraco.com> wrote: Surely some depend on the expectation to overwrite. Most of our tests run under Jenkins where the junitxml file is left around to be processed by Jenkins later. I believe that's the expected behavior for most testing frameworks that generate jUnit XML. > -----Original Message----- > From: Pytest-dev [mailto:[2]pytest-dev- > bounces+jaraco=[3]jaraco....@python.org] On Behalf Of > [4]achart...@fastmail.fm > Sent: Tuesday, 21 January, 2014 17:09 > To: [5]pytest-dev@python.org > Subject: [pytest-dev] Changing the behavior of --junitxml > > Hi, > > I would like to propose a change to the behavior of the --junitxml option. > > Currently, if the same XML file path is specified for multiple invocations of > pytest, the file is overwritten. For our use case, we would like the ability to > append new test results to an existing JUnit XML file so we don't lose > previous results. This is important for us, as we are automating calls to pytest > and would like to avoid the need to create a consolidated JUnit XML results > file ourselves (i.e., by specifying a different argument to --junitxml for each > invocation and then consolidating all the separate XML files into a single one > for consumption by our tool). > > Is this behavior change something that could be considered for the next > release of pytest? If other pytest users are relying on the existing overwriting > behavior of --junitxml, perhaps another pytest option could be added to > toggle between overwrite and append behavior. > > Best, > > Alfonso > _______________________________________________ > Pytest-dev mailing list > [6]Pytest-dev@python.org > [7]https://mail.python.org/mailman/listinfo/pytest-dev _______________________________________________ Pytest-dev mailing list [8]Pytest-dev@python.org [9]https://mail.python.org/mailman/listinfo/pytest-dev References 1. mailto:jar...@jaraco.com 2. mailto:pytest-dev- 3. mailto:jaraco....@python.org 4. mailto:achart...@fastmail.fm 5. mailto:pytest-dev@python.org 6. mailto:Pytest-dev@python.org 7. https://mail.python.org/mailman/listinfo/pytest-dev 8. mailto:Pytest-dev@python.org 9. https://mail.python.org/mailman/listinfo/pytest-dev
_______________________________________________ Pytest-dev mailing list Pytest-dev@python.org https://mail.python.org/mailman/listinfo/pytest-dev
