Is your feature request related to a problem? Please describe.
I use Gitlab CI to automate exporting to various platforms and also run gdUnit3 tests. I check the return code to detect any errors. It's working fine. But it's tedious to look at the logs/report html to find specific failed tests and error logs.
Describe the solution you'd like
An option to write JUnit XML reports instead of HTML ones. They are supported by a wide variety of testing frameworks and automation systems including Jenkins and Gitlab CI.
Describe alternatives you've considered
Interpreting the HTML reports would be possible.
Is your feature request related to a problem? Please describe. I use Gitlab CI to automate exporting to various platforms and also run gdUnit3 tests. I check the return code to detect any errors. It's working fine. But it's tedious to look at the logs/report html to find specific failed tests and error logs.
Describe the solution you'd like An option to write JUnit XML reports instead of HTML ones. They are supported by a wide variety of testing frameworks and automation systems including Jenkins and Gitlab CI.
Describe alternatives you've considered Interpreting the HTML reports would be possible.
Additional context Integration in Gitlab CI: https://docs.gitlab.com/ee/ci/unit_test_reports.html#how-it-works
Official JUnit XML docs: https://www.ibm.com/docs/en/developer-for-zos/14.1.0?topic=formats-junit-xml-format
WAT has some example junit xml export code that could help in implementing this feature for gdUnit3. https://github.com/AlexDarigan/WAT/blob/main/addons/WAT/io/junit_xml.gd