René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"test_runner: JUnit reporter omits the `timestamp` attribute on `\u003ctestsuite\u003e`","articleBody":"### Problem\n\nThe JUnit reporter (`node --test --test-reporter=junit`) emits `\u003ctestsuite\u003e` elements without the `timestamp` attribute defined by the JUnit/Ant XML schema. `timestamp` records, in ISO 8601, when the suite started; Node never writes it.\n\n### Why it matters\n\n`\u003ctestsuite timestamp\u003e` is how JUnit-consuming tools (CI dashboards, test-report viewers) anchor each suite on a time axis — for example, to order suites coming back from parallel/sharded runs, and to build per-suite history and trends across runs. Without it, consumers fall back to file mtime or the overall job time, which is coarser and can be misleading.\n\nNode is also an outlier among JUnit producers: pytest (`--junitxml`), `jest-junit`, `mocha-junit-reporter`, and Maven Surefire all emit `timestamp` on `\u003ctestsuite\u003e`. Node's reporter already emits `time` and `hostname` on `\u003ctestsuite\u003e` (and `file` on `\u003ctestcase\u003e`), but not `timestamp`.\n\n### Current behavior\n\n```console\n$ node --test --test-reporter=junit ...\n\u003ctestsuite name=\"my suite\" time=\"0.42\" disabled=\"0\" errors=\"0\" tests=\"2\" failures=\"0\" skipped=\"0\" hostname=\"...\"\u003e\n```\n\nNo `timestamp` attribute is present.\n\n### Proposed solution\n\nIn `lib/internal/test_runner/reporter/junit.js`, emit the suite start time as the `timestamp` attribute on each `\u003ctestsuite\u003e`.\n\nThere is one open question — the value format:\n\n- **Full ISO 8601 with timezone** (e.g. `2026-06-20T12:34:56.789Z`). This is what `Date.prototype.toISOString()` produces directly, it is unambiguous about the instant, and it is the direction newer tooling (pytest 8.x, Maven Surefire 3.5.5+) is moving.\n- **Legacy no-timezone Ant form** (e.g. `2026-06-20T12:34:56`). This is the canonical de-facto format (Ant `XMLJUnitResultFormatter`; the strict windyroad JUnit XSD even pins it to `\\d{4}-\\d{2}-\\d{2}T\\d{2}:\\d{2}:\\d{2}` with no zone) and what `jest-junit` / `mocha-junit-reporter` currently emit, but it is ambiguous about the actual instant.","author":{"url":"https://github.com/Han5991","@type":"Person","name":"Han5991"},"datePublished":"2026-06-20T14:06:03.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":1},"url":"https://github.com/64028/node/issues/64028"}