-
Notifications
You must be signed in to change notification settings - Fork 29.7k
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
Global "before" hook never seems to be executed #47518
Labels
test_runner
Issues and PRs related to the test runner subsystem.
Comments
VoltrexKeyva
added
the
test_runner
Issues and PRs related to the test runner subsystem.
label
Apr 12, 2023
the reason is |
@MoLow Yeah, I'd be happy to take this 👍🏽 |
atlowChemi
added a commit
to atlowChemi/node
that referenced
this issue
Apr 16, 2023
Execute the before hook for Test as well, and execute it on root before executing any tests. Fixes: nodejs#47518
atlowChemi
added a commit
to atlowChemi/node
that referenced
this issue
Apr 16, 2023
Execute the before hook for Test as well, and execute it on root before executing any tests. Fixes: nodejs#47518
atlowChemi
added a commit
to atlowChemi/node
that referenced
this issue
Apr 16, 2023
Execute the before hook for Test as well, and execute it on root before executing any tests. Fixes: nodejs#47518
atlowChemi
added a commit
to atlowChemi/node
that referenced
this issue
Apr 16, 2023
Execute the before hook for Test as well, and execute it on root before executing any tests. Fixes: nodejs#47518
atlowChemi
added a commit
to atlowChemi/node
that referenced
this issue
Apr 16, 2023
Execute the before hook for Test as well, and execute it on root before executing any tests. Fixes: nodejs#47518
atlowChemi
added a commit
to atlowChemi/node
that referenced
this issue
Apr 16, 2023
Execute the before hook for Test as well, and execute it on root before executing any tests. Fixes: nodejs#47518
nodejs-github-bot
pushed a commit
that referenced
this issue
Apr 18, 2023
Execute the before hook for Test as well, and execute it on root before executing any tests. Fixes: #47518 PR-URL: #47586 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Moshe Atlow <[email protected]>
targos
pushed a commit
that referenced
this issue
May 2, 2023
Execute the before hook for Test as well, and execute it on root before executing any tests. Fixes: #47518 PR-URL: #47586 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Moshe Atlow <[email protected]>
danielleadams
pushed a commit
that referenced
this issue
Jul 6, 2023
Execute the before hook for Test as well, and execute it on root before executing any tests. Fixes: #47518 PR-URL: #47586 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Moshe Atlow <[email protected]>
MoLow
pushed a commit
to MoLow/node
that referenced
this issue
Jul 6, 2023
Execute the before hook for Test as well, and execute it on root before executing any tests. Fixes: nodejs#47518 PR-URL: nodejs#47586 Reviewed-By: Benjamin Gruenbaum <[email protected]> Reviewed-By: Moshe Atlow <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
v19.9.0
Platform
Darwin Vercel-Macbook 22.3.0 Darwin Kernel Version 22.3.0: Mon Jan 30 20:38:37 PST 2023; root:xnu-8792.81.3~2/RELEASE_ARM64_T6000 arm64
Subsystem
No response
What steps will reproduce the bug?
Create a test file with:
and run it with something like
node some.test.js
.How often does it reproduce? Is there a required condition?
always
What is the expected behavior? Why is that the expected behavior?
The output should show log messages from
before
once andbeforeAll
twice.What do you see instead?
The outpu shows log messages from
before
never andbeforeAll
twice.Example Output:
Additional information
No response
The text was updated successfully, but these errors were encountered: