Document how to use xcresultparser with Tuist to export test results as .junit or any other format.

For those who might a solution to this, I was able to replace my previous workflow with Fastlane scan with

tuist test --result-bundle-path tests.xcresult 
xcresultparser -o junit tests.xcresult > results.junit
xcresultparser -o cobertura tests.xcresult > coverage.xml

Options can be changed according to appropriate needs (I needed Cobertura for code coverage reports and JUnit for unit tests) After generating those file I was able to upload them back to Azure Devops and see them associated to the current opened PR.

Thanks @stefanomondino for sharing the resulting setup. I think peeling abstractions at the automation layer is a good idea bringing you down to the raw tools where you have full flexibility. It takes a bit of extra code, but it’s worth it.

Just wanted to point out for future references that using Cobertura (for code coverage) or any other data regarding code coverage might be pointless when using selective testing, because you only get a coverage “snapshot” on the tests that where executed on that specific run, and hopefully it’s only a small part of them. It’s already written as a warning box in Tuist documentation pages, but if people land on this issue via Google like I did it’s best to re-state it :)

@pepicrft are you planning to also integrate tests results (with details) on the Cloud console?

are you planning to also integrate tests results (with details) on the Cloud console?

Yes, we’ll focus on that in the following weeks 🙂