Report is not a valid JUnit report about ci-badges-action HOT 1 CLOSED

After some research, I found that JUnit XML test report files can contain:

• A root <testsuites> tag with multiple child <testsuite> tags (what I've seen the most during my browsing)
• A single root <testsuite> tag (maybe not so common but yet valid)

The current implementation is based on report files like this one:

<?xml version="1.0" encoding="UTF-8"?>
<testsuites name="Tests" time="9.891" tests="62" failures="0">
  <testsuite name="mdtodoc" timestamp="2024-04-18T19:12:28" tests="1" file="[...]" time="0.285" failures="0">
    <testcase name="CLI mdtodoc should fail without argument" time="0.284" classname="should fail without argument"></testcase>
  </testsuite>
  <testsuite name="mdtodoc -h/--help" timestamp="2024-04-18T19:12:28" tests="2" file="[...]" time="0.556" failures="0">
    <testcase name="CLI mdtodoc -h/--help should display help (-h)" time="0.285" classname="should display help (-h)"></testcase>
    <testcase name="CLI mdtodoc -h/--help should display help (--help)" time="0.271" classname="should display help (--help)"></testcase>
  </testsuite>
  [...]
</testsuites>

But having the sum of tests and failures in the root <testsuites> tag doesn't seem to be the most common and standard (e.g. the jest-junit package generates a file with testsuites>testsuite>testcase tags hierarchy but doesn't output tests/failures sum in the root <testsuites> tag).

It may be more reliable to sum tests, failures and errors from each <testsuite> tag (whether there is only one at the root or multiple inside a root <testsuites> tag). That would make this loader more standard, thus supporting more report files, including yours (without breaking with mines).

Does it sound good to you?

P.S. Only the first valid report file (starting from the closest to the project root) is actually used to generate the badge. So make sure your test runner generates a single aggregated report file.

from ci-badges-action.