Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
npm test does not detect new test file changes
See original GitHub issueHi
I created a new app using create-react-app. When npm test is run i get following message
I am using node v4.6.1 and npm 2.15.9
No tests found related to files changed since last commit. Press
ato run all tests, or run Jest with--watchAll.Watch Usage › Press a to run all tests. › Press p to filter by a filename regex pattern. › Press q to quit watch mode. › Press Enter to trigger a test run.
Even if the App.test.js file is changed that doesnt trigger the npm test.
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hi I am having the same issue : I get the “No tests found related to files changed since last commit.” error-I see the test passing locally, but when I run the same job with jenkins it says : no tests found" I have compared the workspace of jenkins , src code and the git repo … all have the same code… thanks for any help– And I added a after npm test in the build actions but it did not work I also tried jest --watchAll still it did not work Naveen 👍
If you are running the test from an IDE or have the command stored somewhere. Add a after the command:
npm test a