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

Don't call openBrowser for smoke test #1460

Conversation

tuchk4
Copy link
Contributor

@tuchk4 tuchk4 commented Jan 27, 2017

Nut sure but seems openBrowser should not be called for smoke test

@tuchk4
Copy link
Contributor Author

tuchk4 commented Jan 30, 2017

@EnoahNetzach check this also please. This relate to new e2e tests

@gaearon
Copy link
Contributor

gaearon commented Feb 15, 2017

Hesitant on this one. I'd leave it in.

This increases our coverage for cases like openBrowser itself throwing because of a typo or something.

@Timer
Copy link
Contributor

Timer commented Feb 15, 2017

Could you (in theory) execute BROWSER=none npm run e2e-simple?

@gaearon
Copy link
Contributor

gaearon commented Feb 15, 2017

Yea. That's the workaround I'd suggest for local testing if it's too annoying.

@gaearon gaearon closed this Feb 15, 2017
@lock lock bot locked and limited conversation to collaborators Jan 21, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants