vscode-jest icon indicating copy to clipboard operation
vscode-jest copied to clipboard

The optimal flow for Jest based testing in VS Code

Results 160 vscode-jest issues
Sort by recently updated
recently updated
newest added

Type: Bug VS Code is highlighting an entier line with yellow or red color when there's nothing wrong on that line Extension version: 5.2.3 VS Code version: Code 1.77.1 (Universal)...

stage: awaiting response
need sample repo

The two options to `autoRun.onSave` are "test-file" | "test-src-file". We have a lot of tests so when set to `"test-src-file"`, this can trigger a performance issues when saving certain files....

stage: awaiting response

### Environment 1. `vscode-jest version`: v5.2.3 2. `node -v`: 19.0.0 3. `npm -v` or `yarn --version`: 8.19.2 4. `npm ls jest` or `npm ls react-scripts` (if you haven’t ejected): @ek/[email protected]...

stage: awaiting response

### Environment 1. `vscode-jest version`: [5.2.3] 2. `node -v`: [14.17.2l] 3. `npm -v` or `yarn --version`: [1.22.19l] 4. `npm ls jest` or `npm ls react-scripts` (if you haven’t ejected): [fill]...

stage: awaiting response

### Environment 1. `vscode-jest version`: [5.2.3] 2. `node -v`: [irrelevant] 3. `npm -v` or `yarn --version`: [irrelevant] 4. `npm ls jest` or `npm ls react-scripts` (if you haven’t ejected): [irrelevant]...

My Jest tests require setup and teardown procedures that I currently configure in `yarn pretest` and `yarn posttest` respectively. Is there a way to make this plugin respect that?

The VSCode reported workspace path is unresolved (microsoft/vscode#18837). When the repository is hosted in a path substituted path (e.g. `subst X: C:`), the test path will not be properly translated...

### Environment 1. `vscode-jest version`: v5.1.0 2. `node -v`: v12.22.7 3. `npm -v` or `yarn --version`: npm 6.14.15 4. `npm ls jest` or `npm ls react-scripts` (if you haven’t ejected):...

stage: awaiting response
external-issue

### Environment Jest 29 & PNPM 7 ### Prerequisite - are you able to run jest test from the command line? yes - how do you run your tests from...

enhancement
good first issue

When Test Explorer is filtered to show only tests from the current file (`@doc`), and it's configured as "View as tree", the explorer shows the entire path down to the...

stage: awaiting response