Global jest variables not injected when using `jestCLI` in Atom.
See original GitHub issueDo you want to request a feature or report a bug?
Bug, maybe?
What is the current behavior?
Attempting to use Jest as a runner for testing Atom package.
I’m able to get Atom to run Jest, which begins to run the test files, but none of the global Jest variables get injected into the test files.
ReferenceError: test is not defined
Here is the code being used to call jestCLI()
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
and yarn test
.
Not sure if it is a bug because there is no documentation for the jest-cli
api. I’ll look into moving this into a separate minimal repo soon if required.
What is the expected behavior?
Jest will inject globals into the test script and run them.
Please provide your exact Jest configuration and mention your Jest, node, yarn/npm version and operating system.
Windows 10.0.17025 Build 17025
npm 5.5.1
node 8.9.1
Jest 22.1.1
No Jest configuration except the variables being passed into jestCLI()
versions reported by apm: apm 1.18.12 npm 3.10.10 node 6.9.5 x64 atom 1.23.3 python 3.6.4 git 2.14.2.windows.2 visual studio
versions reported by Atom Atom : 1.23.3 Electron: 1.6.15 Chrome : 56.0.2924.87 Node : 7.4.0
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (2 by maintainers)
Top GitHub Comments
Oh, haha. I see why you wanted a more descriptive title. I swear I typed a real title the first time. I remember it word for word. 🙈
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. Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.