Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

additional command line parameters #556

Closed
xenoterracide opened this issue Feb 26, 2020 · 2 comments
Closed

additional command line parameters #556

xenoterracide opened this issue Feb 26, 2020 · 2 comments

Comments

@xenoterracide
Copy link

we have an issue in our codebase, which I'm pretty sure is caused by firebase, but a single test doesn't exit properly, then have to kill it. adding --forceExit to the command line seems to fix this, but I see no way to add this in this plugin.

@connectdotz
Copy link
Collaborator

hmmm... you should be able to do this by customizing the jest.pathToJest in your .vscode/settings.json file. Basically you can instruct this extension to run whatever jest command you want with this setting, for example, to run you test script in package.json, which has the --forceExit flag, you can just set"jest.pathToJest": yarn test or run jest directly: "jest.pathToJest": xxx/node_modules/.bin/jest --forceExit

@connectdotz connectdotz mentioned this issue Apr 29, 2020
15 tasks
@seanpoulter seanpoulter added this to the v4.0 milestone May 2, 2020
@connectdotz connectdotz removed this from the v4.0 milestone Jan 14, 2024
@connectdotz
Copy link
Collaborator

close as staled issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants