[pytest-dev] junitxml update

Bruno Oliveira nicoddemus at gmail.com
Thu Aug 16 08:04:48 EDT 2018

Hi folks,

On Thu, Aug 16, 2018 at 2:19 AM RonnyPfannschmidt <
opensource at ronnypfannschmidt.de> wrote:

> Hi Rusty,
> my basic idea to move it forward is to remove it from the pytest core so
> it has freedom to evolve,
> and then getting interested parties to actually work on it as they see fit.

I have a different take on this. I believe moving the plugin out of the
core won't automatically fix its issues. We need to get interested people
involved anyway (like Rusty is offering), and nothing prevents them to
contribute to the core. My main point is that this not a technical issue
IMHO, it is a matter of getting people to contribute, and just taking it
out of the core in a separate plugin won't really help that.

There's also a technical problem involved, because in order to preserve
backward compatibility, pytest will now need to depend on the external
plugin, and I don't think that cross dependency is healthy.

Also the issues don't look too bad to me, and hopefully they can all be
fixed without too much problems if someone would step up.

(i for one aren't interested in working on junitxml at all, i just
> recognize that right now its broken for users and has no-one working on
> fixing that situation)

Fair enough. We use it everyday at work with Jenkins but I just checked and
we are stuck in xUnit 1.1, I guess that's why it has not being bothering
me. :P


> -- Ronny
> Am 14.08.2018 um 20:18 schrieb Rusty Howell:
> Hey all,
> I am interested in working on junitxml. There are several bugs right now
> relating to it.
> https://github.com/pytest-dev/pytest/issues/3777
> https://github.com/pytest-dev/pytest/issues/3547
> https://github.com/pytest-dev/pytest/issues/1862
> https://github.com/pytest-dev/pytest/issues/1126
> In the comments in those bugs, there are some big ideas about the path
> forward, but I'd like to have a more consolidated space for those ideas.
> My end goal would be to have xml output that is compatible with the Jenkins
> Junit Test Report plugin.  We may even have to support multiple versions of
> the plugin. Additionally, there are certainly other xUnit style tools that
> my be slightly different than Junit.
> Ronny mentioned in one of the bugs the idea of Pytest creating a
> serialized test log, and then have an Junitxml plugin consume the
> serialized data and reformat/output as needed. To me it seems that perhaps
> this could be analogous to logging Loggers and Handlers, where a handler
> could be specific, like "Jenkins Junit Test Report v1.3" vs "Jenkins Junit
> Test Report v1.4", or "Allure 2.6.0", etc.
> What are the general thoughts on the path forward for junitxml?
> Thanks
> _______________________________________________
> pytest-dev mailing listpytest-dev at python.orghttps://mail.python.org/mailman/listinfo/pytest-dev
> _______________________________________________
> pytest-dev mailing list
> pytest-dev at python.org
> https://mail.python.org/mailman/listinfo/pytest-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/pytest-dev/attachments/20180816/eaf601bd/attachment-0001.html>

More information about the pytest-dev mailing list