-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
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
process.cwd is not mocked for path.resolve #5146
Comments
Here is the place in |
Demo of how it works in vanilla node: https://repl.it/@borodean/jest-issue-process-cwd-node |
Yep; looks like it's caused by the fact that the |
Closing as dupe of #2549 then |
@SimenB sorry to react to a closed issue, but I looked at the referenced issue and cannot figure out how the two are related and if any progress has been made. I'm running into the same problem with mocking |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Do you want to request a feature or report a bug?
Bug.
What is the current behavior?
path.resolve
ignores mockedprocess.cwd
.If the current behavior is a bug, please provide the steps to reproduce and
either a repl.it demo through https://repl.it/languages/jest or a minimal
repository on GitHub that we can
yarn install
andyarn test
.Demo: https://repl.it/@borodean/jest-issue-process-cwd
What is the expected behavior?
path.resolve
should resolve from the mocked current directory.Please provide your exact Jest configuration and mention your Jest, node,
yarn/npm version and operating system.
Jest 22.0.3
node 8.9.3
npm 5.6.0
Ubuntu 16.04.3 LTS
The text was updated successfully, but these errors were encountered: