Repository navigation
Test Runner run() should support env option #60709
Copy link
Copy link
Closed
Labels
feature requestIssues requesting new Node.js features.Issues requesting new Node.js features.test_runnerIssues and PRs related to the test runner subsystem.Issues and PRs related to the test runner subsystem.
Description
Activity
- addedfeature requestIssues requesting new Node.js features.Issues requesting new Node.js features.
on Nov 13, 2025 - addedtest_runnerIssues and PRs related to the test runner subsystem.Issues and PRs related to the test runner subsystem.
on Nov 13, 2025 I will contribute this
Reacted by Moshe Atlow and Talaviya RonakHey @Ethan-Arrowood, we don't usually assign issues 😁
Any news about the state of the issue? 😀Yeah - I gave it a try a while back but wasn't able to solve it immediately and had more important things to do so its got bumped down my list. Still planning to fix it eventually. Very actively relying on this behavior in my open source work here HarperFast/harper#27
Reacted by Pietro MarchiniReacted by Pietro Marchini- added a commit that references this issue
on Jan 29, 2026 - added 2 commits that reference this issue
on Feb 2, 2026 - added 2 commits that reference this issue
on Feb 10, 2026 - added a commit that references this issue
on Feb 22, 2026
Metadata
Metadata
Assignees
Labels
feature requestIssues requesting new Node.js features.Issues requesting new Node.js features.test_runnerIssues and PRs related to the test runner subsystem.Issues and PRs related to the test runner subsystem.
Type
Projects
- StatusShow more project fieldsAwaiting Triage
What is the problem this feature will solve?
Programmatic configuration of environment variables for test runner.
What is the feature you are proposing to solve the problem?
Add a
envoption similar to that inspawnorexecWhat alternatives have you considered?
My current work around is to just set env variables directly before calling
run().