Title: Can't set `classname` for `testcase` element in JUnit XML when using `node:test` · Issue #59417 · nodejs/node · GitHub
Open Graph Title: Can't set `classname` for `testcase` element in JUnit XML when using `node:test` · Issue #59417 · nodejs/node
X Title: Can't set `classname` for `testcase` element in JUnit XML when using `node:test` · Issue #59417 · nodejs/node
Description: Version v24.4.1 Platform Microsoft Windows NT 10.0.19045.0 x64 Subsystem test What steps will reproduce the bug? Create any test file, like import { suite, test } from "node:test"; await suite('suiteName', () => { test('testName', () => ...
Open Graph Description: Version v24.4.1 Platform Microsoft Windows NT 10.0.19045.0 x64 Subsystem test What steps will reproduce the bug? Create any test file, like import { suite, test } from "node:test"; await suite('sui...
X Description: Version v24.4.1 Platform Microsoft Windows NT 10.0.19045.0 x64 Subsystem test What steps will reproduce the bug? Create any test file, like import { suite, test } from "node:test"; await ...
Opengraph URL: https://github.com/nodejs/node/issues/59417
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Can't set `classname` for `testcase` element in JUnit XML when using `node:test`","articleBody":"### Version\n\nv24.4.1\n\n### Platform\n\n```text\nMicrosoft Windows NT 10.0.19045.0 x64\n```\n\n### Subsystem\n\ntest\n\n### What steps will reproduce the bug?\n\n1. Create any test file, like\n\n ```typescript\n import { suite, test } from \"node:test\";\n \n await suite('suiteName', () =\u003e {\n test('testName', () =\u003e {});\n });\n ```\n\n2. Run the test via console\n\n ```powershell\n node --test --test-reporter=junit \".\\src\\junit.test.mts\"\n ```\n\n3. Check the report from stdout.\n\n### How often does it reproduce? Is there a required condition?\n\nAlways. Regardless the suite or test function arguments.\n\n### What is the expected behavior? Why is that the expected behavior?\n\nThere should be a way to set `classname` value for the JUnit report.\n\nAs of JUnit XML specification, `classname` is\n\n\u003e Full class name for the class the test method is in.\n\nFor example, GitLab uses `classname` when rendering the test reports.\n\nhttps://docs.gitlab.com/ci/testing/unit_test_reports/\n\n\u003e The testcase classname attribute is used as the suite name, not the testsuite name attribute.\n\n### What do you see instead?\n\n```xml\n \u003ctestcase name=\"testName\" time=\"0.000363\" classname=\"test\"/\u003e\n```\n\n`classname` is always `\"test\"`.\n\n### Additional information\n\nI guess currently there's no way to set `classname` in a test event, so reports always get `\"test\"` instead:\n\nhttps://github.com/nodejs/node/blob/931ec10d87730925f0baf10a571330459a1a2fcd/lib/internal/test_runner/reporter/junit.js#L118","author":{"url":"https://github.com/CuriousStork","@type":"Person","name":"CuriousStork"},"datePublished":"2025-08-09T10:17:09.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":8},"url":"https://github.com/59417/node/issues/59417"}
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:8afe7b08-7e31-369a-e275-a28900412c44 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | A3E4:38FD49:9B060:CEEFB:6A4D2E38 |
| html-safe-nonce | 976b2df77af40677ba56202d7aa5b045b6c15977ff774ff31f4ba7b2fdb2c897 |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJBM0U0OjM4RkQ0OTo5QjA2MDpDRUVGQjo2QTREMkUzOCIsInZpc2l0b3JfaWQiOiIyNDQ2NDY2NDAzNTQ2MjQ2NzEyIiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0= |
| visitor-hmac | 70c4abc8cdb4b4734257e2b763546548b0b4f7dc37816c7fb58fb31178ac429d |
| hovercard-subject-tag | issue:3306197937 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/nodejs/node/59417/issue_layout |
| twitter:image | https://opengraph.githubassets.com/24cc18a28b588c7c144a618e87c256a2d20953e51a7fed0d222ff2be24b75000/nodejs/node/issues/59417 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/24cc18a28b588c7c144a618e87c256a2d20953e51a7fed0d222ff2be24b75000/nodejs/node/issues/59417 |
| og:image:alt | Version v24.4.1 Platform Microsoft Windows NT 10.0.19045.0 x64 Subsystem test What steps will reproduce the bug? Create any test file, like import { suite, test } from "node:test"; await suite('sui... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | CuriousStork |
| hostname | github.com |
| expected-hostname | github.com |
| None | 92571a8944142227b7e19cd10918b1ddd06e5066c1ad5bc7e4769cf6140a87e6 |
| turbo-cache-control | no-preview |
| go-import | github.com/nodejs/node git https://github.com/nodejs/node.git |
| octolytics-dimension-user_id | 9950313 |
| octolytics-dimension-user_login | nodejs |
| octolytics-dimension-repository_id | 27193779 |
| octolytics-dimension-repository_nwo | nodejs/node |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 27193779 |
| octolytics-dimension-repository_network_root_nwo | nodejs/node |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 93f17a978ee60bc4668e1d7b90e6bd2d622261fd |
| ui-target | full |
| theme-color | #1e2327 |
| color-scheme | light dark |
Links:
Viewport: width=device-width