New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"logIncompleteSkipped" option is missing since version 6.0 #2779
Comments
This should have been reported on the phpunit-documentation project. I am sorry that I have to close this issue here as GitHub does not support moving issues from one project to another. |
I didn`t know if this option had been intentionally removed or it is just a bug. It is a pity that you decided to remove it. In my opinion it is sometimes useful, in my case for example, Jenkins has problem with parsing |
The ChangeLog reads "The logfile format generated using the --log-junit option and the configuration directive has been updated to match the current format used by JUnit. Due to this change you may need to update how your continuous integration server processes test result logfiles generated by PHPUnit." |
Ran into the same problem. @more7dev did you manage to find a workaround for it? |
My workaround is to remove <skipped/> tags from generated junit.xml, so that Jenkins can successfully parse them. I do it in my CI script, after running phpunit: I see corresponding Jenkins issue still not fixed... |
@more7dev worked great 👍 thanks However, now junit handler seems working! Just replace phpunit handler by junit handler. |
In current manual there is an option described, named "logIncompleteSkipped".
Prior to version 6.0 it was present in Configuration.php file.
Since 6.0 it disappeared from Configuration.php and setting this option has no effect on jUnit output xml.
configuration.xml:
junit.xml - information about skipped tests is still present:
The text was updated successfully, but these errors were encountered: