[JIRA] (JENKINS-51919) jUnit output of PHPUnit test fail to parse

[larsskj@java.net (JIRA)]

larsskj created an issue

Jenkins / JENKINS-51919 jUnit output of PHPUnit test fail to parse Issue Type: Bug Assignee: Nikolas Falco Components: xunit-plugin Created: 2018-06-13 13:32 Environment: Jenkins 2.127 xUnit plugin 2.0.2 Priority: Major Reporter: larsskj Job log show lots of error lines starting like: INFO: [JUnit] - 2 test report file(s) were found with the pattern 'phpunit-result.xml, selenium.xml' relative to '/var/lib/jenkins/workspace/bob-develop' for the testing framework 'JUnit'. WARNING: The file '/var/lib/jenkins/workspace/bob-develop/phpunit-result.xml' is an invalid file. WARNING: At line 3 of file:/var/lib/jenkins/workspace/bob-develop/phpunit-result.xml:cvc-complex-type.3.2.2: Attribute 'assertions' is not allowed to appear in element 'testsuite'. I can supply a full XML file if needed. Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[larsskj@java.net (JIRA)]

larsskj updated an issue

Jenkins / JENKINS-51919 jUnit output of PHPUnit test fail to parse

Change By: larsskj

Job log show lots of error lines starting like:

{code:java}

INFO: [JUnit] - 2 test report file(s) were found with the pattern 'phpunit-result.xml, selenium.xml' relative to '/var/lib/jenkins/workspace/bob-develop' for the testing framework 'JUnit'. WARNING: The file '/var/lib/jenkins/workspace/bob-develop/phpunit-result.xml' is an invalid file. WARNING: At line 3 of file:/var/lib/jenkins/workspace/bob-develop/phpunit-result.xml:cvc-complex-type.3.2.2: Attribute 'assertions' is not allowed to appear in element 'testsuite'.

{code}

I can supply a full XML file if needed.

Add Comment

[nfalco79@hotmail.com (JIRA)]

Nikolas Falco commented on JENKINS-51919

Re: jUnit output of PHPUnit test fail to parse assertions is not a valid attribute of supported JUnit XML report.

Add Comment

[nfalco79@hotmail.com (JIRA)]

Nikolas Falco updated an issue

Jenkins / JENKINS-51919

jUnit output of PHPUnit test fail to parse

Change By: Nikolas Falco Comment:

assertions is not a valid attribute of supported JUnit XML report.

Add Comment

[nfalco79@hotmail.com (JIRA)]

Nikolas Falco closed an issue as Not A Defect

Assertions is not a valid attribute for the testsuite element of supported JUnit report. The managed scenarios are errors, failure and skipped What assertions means? If you would support the custom junit format for phpunit test please select the "Custom Tool" as test type and provide an XSL to conver the generated report to a correct format of the supported JUnit format. In the "custom stylesheet" value you could insert the path of your XSL file that could be absolute on the server (master) or relative to the workspace.

Jenkins / JENKINS-51919 jUnit output of PHPUnit test fail to parse

Change By: Nikolas Falco Status: Open Closed Resolution: Not A Defect

Add Comment

[nfalco79@hotmail.com (JIRA)]

Nikolas Falco commented on JENKINS-51919

Re: jUnit output of PHPUnit test fail to parse Consider to use the internal PHPUnit support instead of leave PHP to produce a compatible report.

Add Comment

[larsskj@java.net (JIRA)]

larsskj commented on JENKINS-51919

Re: jUnit output of PHPUnit test fail to parse

It did work with xUnit 1.X though. I think you should provide a very clear warning when you break backwards compatibility - and provide a way to keep the old version until we've had a chance to resolve the issue. The 1.X -> 2.X upgrade has broken a lot of existing functionality.

Add Comment

[nfalco79@hotmail.com (JIRA)]

Nikolas Falco commented on JENKINS-51919

Re: jUnit output of PHPUnit test fail to parse

As you suggest I mark the plugin to show a warning since version 2.0 and a clear message in the wiki page.

Add Comment

[captainhypertext@gmail.com (JIRA)]

Captain Hypertext commented on JENKINS-51919

Re: jUnit output of PHPUnit test fail to parse

Yeah, this issue completely butchered my unit test parsing.  I switched to the PHPUnit-X parser and it worked pretty well, still using JUnit output.

Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)