Run and debug your Jest tests with ease from VS Code

A VS Code extension that will help you run and debug Jest tests from your editor. You no longer have to run your entire test suite for that one test you changed 🎉

1. Install the extension.
2. Open the test file.
3. Run tests.

1. You don't see the run/link buttons: If you are not seeing the buttons for running the tests, it could be because the plugin did not recognize the file as a test file. You need to update the test match patterns so that it will be recognized as a test file. See the config options section to see more details.

2. Your Jest is installed differently: There is a config option to specify your Jest path. See the config options.

3. Jest does not match your test when you run it from the CodeLens Jest on Windows has different treatment for single and double quotes in command-line arguments.

   The following command may NOT work on Windows because test name is wrapped with apostrophee: node_modules\.bin\jest 'c:/samples/my service/test/get-data.spec.js'

   No tests found, exiting with code 1
   Run with `--passWithNoTests` to exit with code 0
   In C:\samples\my service
   53 files checked.
   testMatch: **/__tests__/**/*.[jt]s?(x), **/?(*.)+(spec|test).[tj]s?(x) - 1 match
   testPathIgnorePatterns: \\node_modules\\ - 35 matches
   testRegex:  - 0 matches
   Pattern: 'c:\\samples\\my service\\test\\get-data.spec.js' - 0 matches

   Wrapping file name with quotation marks solves the problem: node_modules\.bin\jest "c:/samples/my service/test/get-data.spec.js"

   There is a config option to control quotation marks to use in command-line arguments. See the config options.