Skip to content

Conversation

joyeecheung
Copy link
Member

This seems to be a underdocumented but useful trick that only very few people know about. Also add a pointer to the test running guide in the test writing guide.

This seems to be a underdocumented but useful trick that only very few
people know about. Also add a pointer to the test running guide in
the test writing guide.
@nodejs-github-bot
Copy link
Collaborator

Review requested:

  • @nodejs/build
  • @nodejs/tsc

@nodejs-github-bot nodejs-github-bot added build Issues and PRs related to build files or the CI. doc Issues and PRs related to the documentations. labels Oct 15, 2025
Copy link
Member

@richardlau richardlau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

FWIW the test/ prefix is optional and can be omitted, e.g.

tools/test.py parallel/test-stream-*

works.
(IIRC originally the prefix-less (no test/) syntax was the originally supported syntax, and the ability to include the test/ prefix was added later.)

@legendecas
Copy link
Member

In certain shells, the wildcard should be quoted:

$ tools/test.py 'parallel/test-stream-*'

I use this pattern a lot, without test/ prefix.

@joyeecheung
Copy link
Member Author

In certain shells, the wildcard should be quoted:

Yes, that's mentioned in the examples

@joyeecheung
Copy link
Member Author

(IIRC originally the prefix-less (no test/) syntax was the originally supported syntax, and the ability to include the test/ prefix was added later.)

Added a few more examples without the prefix (I used the one with the prefix a bit more often because I tend to copy the relative path from vscode)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build Issues and PRs related to build files or the CI. doc Issues and PRs related to the documentations.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants