Parse and display junit.xml files in the UI when produced as workflow artifacts

[chabala]

Various Java test tools produce junit.xml files as a de facto standard for test output.

CI tools like Hudson/Jenkins, Bamboo, and TeamCity all know how to read junit.xml files and produce meaningful test result displays, often tracking the results of individual tests from run to run.

Can Argo Workflows do this? I can't find any evidence that it can, though there seems to be a rumor that if a junit.xml file is produced as a workflow artifact, it will get parsed, but my experiments with v3.6.18 have all failed to produce anything, only displaying the raw XML file.

If I need (to build) another tool to display test results, that defeats moving to Argo Workflows from 'legacy' CI platforms.

The UI has a 'Give feedback' link that points at closed issue #7743.

[meeraa108]

Big +1 for this. Visualising test results is a core requirement for any CI/CD platform. While Argo is powerful for orchestration, the lack of native junit.xml parsing makes it difficult to fully transition away from 'legacy' tools like Jenkins or TeamCity.

Providing a first-class UI for test reports would significantly improve the developer and QA experience and help teams fully commit to Argo for their entire build pipeline.