test: add file attribute to JUnit reporter testcase elements

[Han5991]

Fixes: #59422

This PR adds support for the file attribute in JUnit XML reporter's testcase elements, addressing the missing source file information that is useful for CI/CD platforms
like GitLab.

Changes

• Add file attribute normalization infrastructure in test output transform
• Implement file attribute support in JUnit reporter for testcase elements
• Include comprehensive tests to verify correct file path handling

Background

The JUnit XML specification supports a file attribute on testcase elements to indicate the source file containing the test. This attribute was missing from Node.js test
runner's JUnit output, limiting integration with tools that rely on this information for enhanced test reporting.

Before:

<testcase name="testName" time="0.000414" classname="test" failure="Failed">

After:
<testcase name="testName" time="0.000414" classname="test" file="src/junit.test.mts" failure="Failed">

Testing

• All existing tests pass
• New tests verify file attribute is correctly included
• File path normalization works across platforms

[nodejs-github-bot]

Review requested:

• @nodejs/test_runner

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 88.54%. Comparing base (b757a8f) to head (6509a5e).
⚠️ Report is 8 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main   #59432   +/-   ##
=======================================
  Coverage   88.53%   88.54%           
=======================================
  Files         703      703           
  Lines      207804   207807    +3     
  Branches    40005    40005           
=======================================
+ Hits       183989   184005   +16     
+ Misses      15817    15811    -6     
+ Partials     7998     7991    -7     

Files with missing lines	Coverage Δ
lib/internal/test_runner/reporter/junit.js	94.47% <100.00%> (+0.10%)	⬆️

... and 25 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Han5991]

@MoLow

Force pushed to fix commit message lint error - shortened title to meet 72 character limit per Node.js contribution guidelines.

[Han5991]

Force pushed to fix commit message lint error - shortened title to meet 72 character limit per Node.js contribution guidelines.

[atlowChemi]

@Han5991 Thanks for the contribution!
The submodule of the second commit should be test_runner, not test (test is the repo's tests themself, while test_runner is node's node:test module 🙂)

[Han5991]

@atlowChemi

Thank you! The submodule reference has been successfully changed from "test" to "test_runner" in the second commit message.

[atlowChemi]

@atlowChemi

Thank you! The submodule reference has been successfully changed from "test" to "test_runner" in the second commit message.

They seem to be applied the wrong way?
The commit which handles the tests is currently test_runner, and the one changing the test runner is test

[Han5991]

@atlowChemi
Thank you! The submodule reference has been successfully changed from "test" to "test_runner" in the second commit message.

They seem to be applied the wrong way? The commit which handles the tests is currently test_runner, and the one changing the test runner is test

@atlowChemi
Thank you for checking! I've reapplied the changes with the correct commit message prefixes - now the test_runner module changes use test_runner: and the test preparation changes use test:.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/68690/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/69263/

[Han5991]

@atlowChemi

One of the CI jobs seems to have failed due to a flaky test. Would you mind rerunning just the failed job when you have a chance?

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/69609/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/69611/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/69612/

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/69613/

[nodejs-github-bot]

Landed in 1527825...f0aa073