tag:help.appveyor.com,2012-11-13:/discussions/suggestions/5298-support-ctest-xml-test-resultsAppVeyor: Discussion 2018-08-25T02:26:13Ztag:help.appveyor.com,2012-11-13:Comment/444179202018-01-03T02:16:52Z2018-01-03T02:16:52ZSupport CTest XML test results<div><p>It is pretty easy to do this on-the-fly with information you provided. Please check <a href="https://gist.github.com/IlyaFinkelshteyn/237ef33c8c94057f0c4af1155e9bb043">sample yaml</a> demonstrating how to do this. <a href="https://ci.appveyor.com/project/IlyaFinkelshteyn/projecta/build/33.464.915">Here</a> is build demonstrating this in work.<br>
Sure in real life you do not need to download <code>Test.xml</code> as it will be created by your tests, and also you can choose to check-in <code>ctest-to-junit.xsl</code> instead of loading remote file every time.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/444179202018-01-03T11:27:53Z2018-01-03T11:27:54ZSupport CTest XML test results<div><p>Thanks for that Powershell magic Ilya. It’s working well for me here. It would be useful to have this information in the Appveyor docs perhaps (could also add info on googletest/gtest which makes junit compatible xml by default).</p></div>Harry Mallontag:help.appveyor.com,2012-11-13:Comment/444179202018-01-03T22:28:52Z2018-01-03T22:28:52ZSupport CTest XML test results<div><p>You are very welcome! Right, we have to add this. By the way, our <a href="https://github.com/appveyor/website/blob/master/src/docs/running-tests.md">site is open source</a> so feel free to send a PR if you have time for this :)</p></div>Ilya Finkelshteyn