-
-
Notifications
You must be signed in to change notification settings - Fork 214
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
xml output #10
Comments
I agree. Let's get the ball rolling on this one. I'm thinking the exact same switch --log-junit? |
That'd be great. I'm thinking the best way to do this would be to gather all the XMLs from concurrent runs (like above) but then combine with with SimpleXML or the like to get it into 1 file. |
I actually have something along those lines in progress right now. Since XML files need to be evaluated at run time (for the live feedback - .EF....E) I am working on aggregating those results so when the run ends they can just be dumped to an XML file. I am rewriting the JUnit log reader to give back data structures for individual test suites and their cases, so dumping that to XML should be a snap. I should have this pushed and tagged by the weekend. |
Ok sorry about the delay. This has been pushed to dev-master if you feel like giving it a shot. If things look good to you, I will tag it and update packagist to use the newest version. Thanks! |
As far as I can gather from my tests, it is all good. I am going to tag a 0.3.0 release and push it. If something is behaving strangely, we can definitely open another issue. |
jlipps sent me here -
phpunit has JUnit XML output to be parsed by things like Jenkins. With paraunit, I hacked it so that each phpunit process would dump it's own XML to a folder that Jenkins would parse. It would be nice to standardize this a little bit to get it to be identical to the same XML returned by a plain phpunit run.
The text was updated successfully, but these errors were encountered: