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

Hide Chrome when running in command line-OS X #4219

Closed
nataliejuner opened this issue May 16, 2019 · 2 comments
Closed

Hide Chrome when running in command line-OS X #4219

nataliejuner opened this issue May 16, 2019 · 2 comments

Comments

@nataliejuner
Copy link

nataliejuner commented May 16, 2019

Current behavior:

When I go to run npx cypress run --browser chrome it will run my test(s) in both the command line AND a Chrome window.

When using npx cypress run it only runs in command line.

Desired behavior:

It would be awesome and easier to simply run tests in the command line only AND to utilize Chrome over Electron as my app does not support Electron.

I asked on stack overflow whether it was possible to be able to run a command to tell Chrome to not run in a window but to defer to Chrome over Electron when running a test in the command line.
Stack Overflow post

I did have a reply saying to run DISPLAY= npx cypress run --browser chrome which would make the display to not show of the Chrome window but it would still utilize it when running in the command line. However, this only works for Linux and not OS X and it's only hiding it from you rather than just running "headless".

Summary

To be able to run a "headless" version of Chrome like Electron with command line testing for OS X users.

Versions

Chrome 74

OS X Mojave 10.14.4

@jennifer-shehane
Copy link
Member

@flotwig, who answered your question on StackOverflow, is one of our engineers - so his answer is as it stands.

I believe you likely want support for this issue to support true Chrome headless: #832

Please let us know if this issue summarizes what you're looking for and close the issue if so.

@cypress-bot cypress-bot bot added the stage: awaiting response Potential fix was proposed; awaiting response label May 17, 2019
@nataliejuner
Copy link
Author

yes it does! Thank you as well as @flotwig for his answers over on stack.

@jennifer-shehane jennifer-shehane removed the stage: awaiting response Potential fix was proposed; awaiting response label May 20, 2019
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

2 participants