The Jest watch plugin system provides a way to hook into specific parts of Jest and to define watch mode menu prompts that execute code on key press. Combined, these features allow you to develop interactive experiences custom for your workflow.
To connect your watch plugin to Jest, add its path under
watchPlugins in your Jest configuration:
Custom watch plugins can add hooks to Jest events. These hooks can be added either with or without having an interactive key in the watch mode menu.
Jest hooks can be attached by implementing the
apply method. This method receives a
jestHooks argument that allows the plugin to hook into specific parts of the lifecycle of a test run.
Below are the hooks available in Jest.
Returns a boolean (or
Promise<boolean> for handling asynchronous operations) to specify if a test should be run or not.
Gets called at the end of every test run. It has the test results as an argument.
Gets called whenever there is a change in the file system
projects: Array<config: ProjectConfig, testPaths: Array<string>: Includes all the test paths that Jest is watching.
Custom watch plugins can also add or override functionality to the watch menu by specifying a key/prompt pair in
getUsageInfo method and a
run method for the execution of the key.
To add a key to the watch menu, implement the
getUsageInfo method, returning a key and the prompt:
This will add a line in the watch mode menu (
› Press s to do something.)
Note: If the key for your plugin already exists as a default key, your plugin will override that key.
To handle key press events from the key returned by
getUsageInfo, you can implement the
run method. This method returns a
Promise<boolean> that can be resolved when the plugin wants to return control to Jest. The
boolean specifies if Jest should rerun the tests after it gets the control back.
globalConfig: A representation of Jest's current global configuration
updateConfigAndRun: Allows you to trigger a test run while the interactive plugin is running.
Note: If you do call
run method should not resolve to a truthy value, as that would trigger a double-run.
For stability and safety reasons, only part of the global configuration keys can be updated with
updateConfigAndRun. The current white list is as follows:
Plugins can be customized via your Jest configuration.
Recommended config names:
key: Modifies the plugin key.
prompt: Allows user to customize the text in the plugin prompt.
If the user provided a custom configuration, it will be passed as an argument to the plugin constructor.
Jest allows third-party plugins to override some of its built-in feature keys, but not all. Specifically, the following keys are not overwritable :
c(clears filter patterns)
i(updates non-matching snapshots interactively)
u(updates all non-matching snapshots)
w(displays watch mode usage / available actions)
The following keys for built-in functionality can be overwritten :
p(test filename pattern)
t(test name pattern)
Any key not used by built-in functionality can be claimed, as you would expect. Try to avoid using keys that are difficult to obtain on various keyboards (e.g.
€), or not visible by default (e.g. many Mac keyboards do not have visual hints for characters such as
, [`, etc.)
Should your plugin attempt to overwrite a reserved key, Jest will error out with a descriptive message, something like:
Watch plugin YourFaultyPlugin attempted to register key
q, that is reserved internally for quitting watch mode. Please change the configuration key for this plugin.
Third-party plugins are also forbidden to overwrite a key reserved already by another third-party plugin present earlier in the configured plugins list (
watchPlugins array setting). When this happens, you’ll also get an error message that tries to help you fix that:
Watch plugins YourFaultyPlugin and TheirFaultyPlugin both attempted to register key
x. Please change the key configuration for one of the conflicting plugins to avoid overlap.