Hi,
the comments in help output i.e tau.h: tau_help_() state "--output= Write an XUnit XML file to Enable XUnit output"
I'm not very familiar with XUnit format is that a specific variant on JUnit format that you are intentional supporting (because Microsoft Azure Devops didn't recognize the file as 'XUnit' i.e. https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/reference/publish-test-results-v2?view=azure-pipelines&tabs=trx%2Ctrxattachments%2Cyaml)
and though the output it is mostly JUnit compatible (all correct if just reporting test passes), it's doesn't add the element to correctly report test failures.
Happy to provide patches/PR to enhance the XML output (i.e. ideally as JUnit as i believe that is the most commonly supported format) just first wanted to check the intention behind the --output option first
Otherwise great test framework, very impressed :)
Chris
Hi,
the comments in help output i.e tau.h: tau_help_() state "--output= Write an XUnit XML file to Enable XUnit output"
I'm not very familiar with XUnit format is that a specific variant on JUnit format that you are intentional supporting (because Microsoft Azure Devops didn't recognize the file as 'XUnit' i.e. https://learn.microsoft.com/en-us/azure/devops/pipelines/tasks/reference/publish-test-results-v2?view=azure-pipelines&tabs=trx%2Ctrxattachments%2Cyaml)
and though the output it is mostly JUnit compatible (all correct if just reporting test passes), it's doesn't add the element to correctly report test failures.
Happy to provide patches/PR to enhance the XML output (i.e. ideally as JUnit as i believe that is the most commonly supported format) just first wanted to check the intention behind the --output option first
Otherwise great test framework, very impressed :)
Chris