Stuck on an issue?

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.

How to run test cases of only the file currently being edited.

See original GitHub issue

Environment

node -v: [fill]
npm -v: [fill]
npm ls jest or npm ls react-scripts (if you haven’t ejected): [fill]
your vscode-jest settings if customized:
- jest.pathToJest? [fill]
- jest.pathToConfig? [fill]
- anything else that you think might be relevant? [fill]
Operating system: [fill]

Prerequisite

are you able to run jest test from command line? [fill]
how do you run your tests from command line? (for example: npm run test or node_modules/.bin/jest) [fill]

Steps to Reproduce

[fill]

Relevant Debug Info

[fill]

Expected Behavior

[fill]

Actual Behavior

[fill]

The fastest (and the most fun) way to resolve the issue is to submit a pull-request yourself. If you are interested, feel free to check out the contribution guide, we look forward to seeing your PR…

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:6 (2 by maintainers)

Top GitHub Comments

5reactions

connectdotzcommented, Apr 1, 2020

Is possible to run only on the currently opened test file?

In theory, once you turned off the jest.runAllTestsFirst, jest should only run the tests that “changed”. However, if you want to run the files opened, regardless if they are changed, which sounded like an 'on-demand" testing… such feature doesn’t exist yet… although I can see it could be useful for some use case… PR is welcome.

1reaction

connectdotzcommented, Apr 6, 2021

@raphaelbs it’s not officially released in the marketplace yet, but you can install it using the VSIX file, please see “How to test” section in v4.0.0-alpha.5 release note.