Incorrent xml output if I use the dataProvider in tests about paratest HOT 12 CLOSED

Awesome thanks for bringing this up. I'll take a look into this. Any issue noticed with running against a directory?

from paratest.

No, I haven't noticed anything unusual yet.

from paratest.

has any ideas when this bug will be fixed?

from paratest.

I can confirm this bug still exists with version 0.12.0 of paratest.

from paratest.

Also experiencing this

from paratest.

Yes, I'd like to vote for this bug as well. Any tips wrt. when this bug will be fixed?

from paratest.

Or, how it could be fixed.

from paratest.

A partly fix is on the way with PR #185

from paratest.

About the "testsuite" elements containing child "testsuite" elements, @drefixs brought up some infos here: #185 (comment)
As phpunit tries to produce junit-like logs and there is no trace that junit logs do or are allowed to contain nested "testsuite"-elements, I agree with @drefixs that phpunit is doing it wrong.

Any opinions on this? Trying to get a fix in all maintained phpunit versions (I think the best we would get is a fix in the next major version because of BC) / adding a flag to produce "wrong" junit logs / ...
Or is this even the core problem of this thread or was it more about empty names etc.?

from paratest.

Jenkins has a separate parser for junit xml logs from PHPUnit. If we can
use the normal one without problems then IMHO that is a win.

2015-11-18 0:08 GMT+01:00 Julian Seeger [email protected]:

About the "testsuite" elements containing child "testsuite" elements,
@drefixs https://github.com/drefixs brought up some infos here: #185
(comment)
#185 (comment)
As phpunit tries to produce junit-like logs and there is no trace that
junit logs do or are allowed to contain nested "testsuite"-elements, I
agree with @drefixs https://github.com/drefixs that phpunit is doing it
wrong.

Any opinions on this? Trying to get a fix in all maintained phpunit
versions (I think the best we would get is a fix in the next major version
because of BC) / adding a flag to produce "wrong" junit logs / ...
Or is this even the core problem of this thread or was it more about empty
names etc.?

—
Reply to this email directly or view it on GitHub
#19 (comment).

Tarjei Huse
Mobil: 920 63 413

from paratest.

@tarjei
just see:
https://svn.jenkins-ci.org/trunk/hudson/dtkit/dtkit-format/dtkit-junit-model/src/main/resources/com/thalesgroup/dtkit/junit/model/xsd/junit-4.xsd (jenkins shema)
https://github.com/windyroad/JUnit-Schema/blob/master/JUnit.xsd (common shema)

Are you see any testsuite into testsuite ? jenkins can parse it but other CI system can't.
Now paratest has my fix for this problem #185 you can try get last version, and test it now.

from paratest.

Seems to be fixed. If anyone disagrees, please open a new issue with new infos what's good and whats missing.

from paratest.