Uh oh, something went wrong? Use this guide to resolve issues with Jest.
Essayez d’utiliser le debugger intégré à Node. Note: This will only work in Node.js 8+.
debugger; dans l’un de vos tests et puis, dans le répertoire de votre projet, exécutez :
This will run Jest in a Node process that an external debugger can connect to. Note that the process will pause until the debugger has connected to it.
To debug in Google Chrome (or any Chromium-based browser), open your browser and go to
chrome://inspect and click on "Open Dedicated DevTools for Node", which will give you a list of available node instances you can connect to. Click on the address displayed in the terminal (usually something like
localhost:9229) after running the above command, and you will be able to debug Jest using Chrome's DevTools.
The Chrome Developer Tools will be displayed, and a breakpoint will be set at the first line of the Jest CLI script (this is done to give you time to open the developer tools and to prevent Jest from executing before you have time to do so). Click the button that looks like a "play" button in the upper right hand side of the screen to continue execution. When Jest executes the test that contains the
debugger statement, execution will pause and you can examine the current scope and call stack.
--runInBandcli option makes sure Jest runs the test in the same process rather than spawning processes for individual tests. Normally Jest parallelizes test runs across processes but it is hard to debug many processes at the same time.
To attach the built-in debugger, run your tests as aforementioned:
Then attach VS Code's debugger using the following
To automatically launch and attach to a process running your tests, use the following configuration:
or the following for Windows:
If you are using Facebook's
create-react-app, you can debug your Jest tests with the following configuration:
More information on Node debugging can be found here.
The easiest way to debug Jest tests in WebStorm is using
Jest run/debug configuration. It will launch tests and automatically attach debugger.
In the WebStorm menu
Edit Configurations.... Then click
+ and select
Jest. Optionally specify the Jest configuration file, additional options, and environment variables. Save the configuration, put the breakpoints in the code, then click the green debug icon to start debugging.
If you are using Facebook's
create-react-app, in the Jest run/debug configuration specify the path to the
react-scripts package in the Jest package field and add
--env=jsdom to the Jest options field.
The transform script was changed or Babel was updated and the changes aren't being recognized by Jest?
--no-cache. Jest caches transformed module files to speed up test execution. If you are using your own custom transformer, consider adding a
getCacheKey function to it: getCacheKey in Relay.
If a promise doesn't resolve at all, this error might be thrown:
Most commonly this is being caused by conflicting Promise implementations. Consider replacing the global promise implementation with your own, for example
global.Promise = jest.requireActual('promise'); and/or consolidate the used Promise libraries to a single one.
If your test is long running, you may want to consider to increase the timeout by calling
Try running Jest with
--no-watchman or set the
watchman configuration option to
Also see watchman troubleshooting.
Based on the findings, one way to mitigate this issue and improve the speed by up to 50% is to run tests sequentially.
In order to do this you can run tests in the same thread using
Another alternative to expediting test execution time on Continuous Integration Servers such as Travis-CI is to set the max worker pool to ~4. Specifically on Travis-CI, this can reduce test execution time in half. Note: The Travis CI free plan available for open source projects only includes 2 CPU cores.
coveragePathIgnorePatterns seems to not have any effect.#
Make sure you are not using the
babel-plugin-istanbul plugin. Jest wraps Istanbul, and therefore also tells Istanbul what files to instrument with coverage collection. When using
babel-plugin-istanbul, every file that is processed by Babel will have coverage collection code, hence it is not being ignored by
Tests must be defined synchronously for Jest to be able to collect your tests.
As an example to show why this is the case, imagine we wrote a test like so:
When Jest runs your test to collect the
tests it will not find any because we have set the definition to happen asynchronously on the next tick of the event loop.
Note: This means when you are using
test.each you cannot set the table asynchronously within a