-
-
Notifications
You must be signed in to change notification settings - Fork 5
doc(minutes): add 09 Feb 2026 #15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
|
||
| ## Outcomes | ||
|
|
||
| * General agreement that `t.skip()`'s behaviour is wrong (likely an accident/bug/mistake, which the docs seem to support). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've just checked the rest of the documentation, and the behavior is definitely intended:
https://nodejs.org/docs/v24.13.0/api/test.html#contextskipmessage.
When checking other test runners, like Mocha, this behavior also exists (e.g. https://mochajs.org/declaring/inclusive-tests/#_top).
Given that this behavior is "by design" and aligned with other test runners,IMHO , it's just a matter of personal preference...and I don't think it's enough to justify a major breaking change
P.S.: the same is true for Vitest as well (https://vitest.dev/guide/test-context.html#test-context)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, interesting. Thanks for checking!
If it's actually fairly common, then sure, it's already there. Kinda weird, but some people like liquorice too 🤷♂️
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We might want to understand how common it is, but I'm not sure that, without a standard, it makes sense to compare different tools...
cc @ljharb
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If these runners all have the API, then that’s a very different story, but it still seems weird to me given the tap-like API the test runner has - which leads into the design philosophy discussion.
|
|
||
| ## Outcomes | ||
|
|
||
| * General agreement that `t.skip()`'s behaviour is wrong (likely an accident/bug/mistake, which the docs seem to support). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| * General agreement that `t.skip()`'s behaviour is wrong (likely an accident/bug/mistake, which the docs seem to support). | |
| * ~Initially general agreement that `t.skip()`'s behaviour is wrong (likely an accident/bug/mistake, which the docs seem to support).~ | |
| * Further investigation shows this behaviour | |
| * exists in others (including [mocha](https://mochajs.org/declaring/inclusive-tests/#_top)) | |
| * was intended: https://nodejs.org/docs/v24.13.0/api/test.html#contextskipmessage |
Closes #14