Skip to content
This repository has been archived by the owner on Dec 14, 2020. It is now read-only.

Specify path to test runner #38

Closed
e0da opened this issue Feb 23, 2019 · 4 comments
Closed

Specify path to test runner #38

e0da opened this issue Feb 23, 2019 · 4 comments

Comments

@e0da
Copy link

e0da commented Feb 23, 2019

First, thank you. I appreciate your work.

Please allow overriding the test runner path. I want to use yarn test as my test runner instead of the detected node_modules/.bin/jest. As it stands, this doesn't work with create-react-app. This is touched on in #29, but I want to be clear that the problem is that you can't override the test runner. If you could override the test runner, it would completely open up the tool to let people do whatever setup/teardown they need when the out of box experience doesn't work. Right now I could maybe futz with Jest or Babel config and get something to work, but those configs are currently hidden by create-react-app (I haven't "ejected" it, and don't want to). But ideally that'd be moot since I already have a solution for this problem: yarn test does everything I need. I'd like to just add something like this to my VSCode user settings.json:

{  "javascript-test-runner.testRunnerPath": "yarn test" }

And in my case, jest is being called underneath so all the rest of the default config can be passed on and work correctly. But today it's just calling the wrong bin. 😿

@wiloke1
Copy link

wiloke1 commented May 11, 2019

I want to do the same

@g3offrey
Copy link
Owner

Hello,

Please accept my apologies for the late answer.
I published a status about this extension. 😞
(TL;DR: I won't be able to work on it anymore)

#41 (comment)

@e0da
Copy link
Author

e0da commented Jun 13, 2019

@g3offrey Well that's ok! Thank you anyway. I appreciate your work.

@felixjb
Copy link

felixjb commented Aug 10, 2019

Hi @justinforce ,
Could you help me understand a little more of how you use yarn test in this case?
I am working on this feature now.

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

No branches or pull requests

4 participants