Support for the PHPUnit dialect of JUnit

[mbeccati]

PHPUnit uses nested <testsuite> elements, and the actual test cases are ignored in the current version of the reporter.

This is my first attempt at TypeScript, so apologies for any silly mistake.

Most likely it would be best to implement it as a separate parser, add more features, such as better error reporting, file links, etc.

As a first prototype, it seems to be working good enough for my current needs, e.g. https://github.com/mbeccati/php-latest-builds/runs/23625536886

[darshanrampatel]

@mbeccati An interesting approach - when I needed to do this, I instead modified the PHPUnit test file to match the JUnit format:

# Change from
#
# <testsuites>
#   <testsuite name="" ...
#   ...
#   </testsuite>
# </testsuites>
#
# to
#
# <testsuites name=""
# ...
# </testsuites>

I think your approach is probably better though 🙂

One thing that I'm not sure "just works" in your version is the file annotations - I had to perform some regex to get this to work. See this: https://github.com/darshanrampatel/test-reporter/blob/e8fa95a4ce020faeb9a198f9b31bf4e6e200c2b9/src/parsers/phpunit-junit/phpunit-junit-parser.ts#L182-L196

(I apologise that it's not documented😅)

[mbeccati]

@darshanrampatel nice! Feel free to borrow from this PR for your fork. That would indeed make for a better PR than this one. If you do, pls let me know. Id'be more than happy to give it a try

[jozefizso]

This should be a new parser specific for PHPUnit format.

[mbeccati]

@jozefizso I agree. I just wasn't sure exacty where to start with a new parser, or at least that's what I recall. It's bee a while ;-)

Are you suggesting I edit the PR creating a new parser? If so I think I'd need some guidance

[pierrelemee]

Faced the same issue so I tested with your changes and it works like a charm ✅ (best approval I can give)

[jozefizso]

This should be a new parser for PHPUnit format.

[jozefizso]

Review findings (from code review):

• High: PHPUnit emits absolute paths, but the parser only accepts exact matches against trackedFiles (repo‑relative from git ls-files). This likely prevents annotations from ever resolving (path/line stay undefined). Consider mapping to repo‑relative via getBasePath (like JestJunitParser) or matching by basename. Ref: src/parsers/phpunit-junit/phpunit-junit-parser.ts:136, src/parsers/phpunit-junit/phpunit-junit-parser.ts:146.
• Medium: Failure details are dropped when <failure> is parsed as a plain string (no attributes). details becomes '', which also blocks file/line extraction from the stack trace. Add a fallback like typeof failure === 'string' ? failure : failure._. Ref: src/parsers/phpunit-junit/phpunit-junit-parser.ts:129.
• Medium: The stack trace regex only matches *.php and ignores .phpt and Windows drive paths, so those traces won’t be parsed even if relative mapping is added. Consider broadening the pattern. Ref: src/parsers/phpunit-junit/phpunit-junit-parser.ts:171.
• Low: README doesn’t list phpunit-junit in supported frameworks or in the reporter options, so the new parser isn’t discoverable. Ref: README.md:15, README.md:141.

[mbeccati]

Brilliant, thanks!