René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"node:test watch mode with isolation: 'none' ignores cwd-scoped discovery and reuses parent argv","articleBody":"### Version\n\n26.2.0\n\n### Platform\n\n```text\nmacOS 26.5.0\n```\n\n### Subsystem\n\nstream\n\n### What steps will reproduce the bug?\n\n```js\nimport { run } from 'node:test';\nimport { mkdtemp, writeFile, readFile } from 'node:fs/promises';\nimport { join } from 'node:path';\nimport { tmpdir } from 'node:os';\n\nconst cwd = await mkdtemp(join(tmpdir(), 'node-test-'));\nconst marker = join(cwd, 'ran');\n\nawait writeFile(join(cwd, 'test.js'), `\n  const test = require('node:test');\n  const { writeFileSync } = require('node:fs');\n  test('from cwd', () =\u003e writeFileSync(${JSON.stringify(marker)}, 'yes'));\n`);\n\nconst ac = new AbortController();\nconst stream = run({\n  cwd,\n  watch: true,\n  isolation: 'none',\n  signal: ac.signal,\n});\n\nstream.on('data', ({ type }) =\u003e {\n  if (type === 'test:watch:drained') ac.abort();\n});\n\nfor await (const _ of stream);\n\nconst ran = await readFile(marker, 'utf8').catch(() =\u003e 'no');\nconsole.log({ ran });\n```\n\n### How often does it reproduce? Is there a required condition?\n\nAlways\n\n### What is the expected behavior? Why is that the expected behavior?\n\n```console\n{ ran: 'yes' }\n```\n\n`run({ cwd, watch: true, isolation: 'none' })` should discover and execute tests from the supplied `cwd`, then report the result of those tests. In the repro, the cwd fixture should run and write the marker file.\n\n### What do you see instead?\n\n```console\n{ ran: 'no' }\n```\n\nThe isolation-none watch child is spawned using the parent process argv while its working directory is changed to the supplied `cwd`. This can run the wrong entry point, recurse into the driver, or execute no intended cwd test, so the marker is not written.\n\n### Additional information\n\nThis is likely the same failure mode behind `test-runner/test-run-watch-cwd-isolation-none`: that test expects one pass from the fixture copied into `tmpdir.path`, but the implementation can spawn a watch child using the outer test’s argv instead of the cwd-scoped fixture. Depending on invocation and tmpdir state, it may report zero passes, fail recursively, or exit with code 1, making the CI failure flaky.","author":{"url":"https://github.com/trivikr","@type":"Person","name":"trivikr"},"datePublished":"2026-06-01T06:36:26.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/63689/node/issues/63689"}