René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"errors thrown in describe() do not set non-zero exitCode (and do not fail CI)","articleBody":"### Version\n\nv24.2.0\n\n### Platform\n\n```text\nDarwin 24.4.0 Darwin Kernel Version 24.4.0: Fri Apr 11 18:34:14 PDT 2025; root:xnu-11417.101.15~117/RELEASE_ARM64_T8122 arm64\n```\n\n### Subsystem\n\ntest\n\n### What steps will reproduce the bug?\n\n```js\nimport { describe, test } from 'node:test'\nimport assert from 'node:assert/strict'\n\ndescribe('green', () =\u003e {\n  test('one', () =\u003e {\n    assert(1 === 1)\n  })\n})\n\ndescribe('red', () =\u003e {\n  test_('one', () =\u003e {\n    assert(1 === 1)\n  })\n\n  test('two', () =\u003e {\n    assert(1 === 2)\n  })\n})\n```\n\n`node --test foo.js; echo $?`\n\n### How often does it reproduce? Is there a required condition?\n\nEvery time\n\n### What is the expected behavior? Why is that the expected behavior?\n\nA test failure printed and a non-zero exit code upon test termination\n\n### What do you see instead?\n\nA test failure printed but the exit code is zero, the test is effectively treated as passing by tooling / CI\n\n### Additional information\n\nA work-around using a custom reporter is possible, see https://github.com/ExodusMovement/test/commit/749370166fe70e51dd60e1c11a012cc64a0b15eb","author":{"url":"https://github.com/ChALkeR","@type":"Person","name":"ChALkeR"},"datePublished":"2025-06-12T04:42:48.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":5},"url":"https://github.com/58687/node/issues/58687"}