No tests found related to files changed since last commit.
See original GitHub issueHi!
I’ve installed the plugin, made sure I got this in package.json:
"test": "jest --watchAll --config node_modules/ca-ui-module-test/__jestDist__/jest.config"
But the runner keeps telling me all the time:
No tests found related to files changed since last commit.
Press `a` to run all tests, or run Jest with `--watchAll`.
I can do yarn test
and everything works normally. Am I missing something? What should I look for? Is there anything I can activate that gives more more info?
Thanks!
Issue Analytics
- State:
- Created 7 years ago
- Reactions:10
- Comments:8 (4 by maintainers)
Top Results From Across the Web
Jest from create-react-app not running on Windows
After the installation, running the command npm run test , I get the error: No tests found related to files changed since last...
Read more >Jest – how works and why we need it? - Learn tech systems
“No tests found related to files changed since last commit.” So the watch mode (npm test) is a way that we can run...
Read more >no tests found related to files changed since last commit.
Jest will always explicitly mention that it only ran tests related to the files changed since the last commit. You can also press...
Read more >Run react-script tests without watch - Marcusoft.net
No tests found related to files changed since the last commit. is the error message that keeps popping up for us. It's not...
Read more >Run jest for unit tests of modified files only | by SunCommander
The problem with this option is that once you commit or push your changes, it won't be able to find changed files so...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
npm test a
@orta It was my mistake. I had to change
pathToJest
inside the workspace settings. I initially didn’t realize that I could set it to a command.If you’d like, I can make a PR making a note of this in the README. Thanks again for your time!