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

Allow passing path to the browser in --browser <path> CLI option #1026

Closed
bahmutov opened this issue Dec 6, 2017 · 9 comments
Closed

Allow passing path to the browser in --browser <path> CLI option #1026

bahmutov opened this issue Dec 6, 2017 · 9 comments
Assignees
Labels
browser: chrome pkg/launcher This is due to an issue in the packages/launcher directory

Comments

@bahmutov
Copy link
Contributor

bahmutov commented Dec 6, 2017

feature

Last unfinished task from #511

Allow the user to pass path to specific browser to use --browser /my/bin/browser

@bahmutov bahmutov self-assigned this Dec 6, 2017
@bahmutov bahmutov added browser: chrome pkg/launcher This is due to an issue in the packages/launcher directory labels Dec 6, 2017
@bahmutov bahmutov added this to the 1.1.4 milestone Dec 6, 2017
@brian-mann
Copy link
Member

You need to also handle the error situation when the browser cannot be found.

The code paths likely already account for this, but at least write one test.

@brian-mann
Copy link
Member

They are likely in integration/cypress_spec.coffee already

@bahmutov
Copy link
Contributor Author

bahmutov commented Dec 7, 2017

it is not as simple as I have hoped, and I was getting an error as I left for meetup :( basically I am passing the browser name all the way down to the launcher and want to either find it by name in the list of detected browsers or try running it as chrome

@brian-mann brian-mann removed this from the 1.1.4 milestone Dec 7, 2017
@bahmutov bahmutov added this to the 1.1.5 milestone Dec 7, 2017
@bahmutov
Copy link
Contributor Author

bahmutov commented Dec 7, 2017

hmm, something is not shutting down browser after it is done testing

@brian-mann brian-mann modified the milestones: 1.1.5, 1.2.1 Dec 12, 2017
@rsudarson
Copy link

rsudarson commented Mar 29, 2018

@bahmutov : I've a path to linux chrome binary, how can i pass options to cypress to pickup this chrome path for testing.

@Aurimas1
Copy link

Aurimas1 commented Jan 17, 2019

Is this feature still in development?

@ethernal
Copy link

I am also interested in this.. how can I for example use Chrom Beta that is installed side by side with stable version?

@cypress-bot
Copy link
Contributor

cypress-bot bot commented Feb 16, 2019

The code for this is done in cypress-io/cypress#3337, but has yet to be released.
We'll update this issue and reference the changelog when it's released.

@cypress-bot cypress-bot bot removed the stage: needs review The PR code is done & tested, needs review label Feb 16, 2019
@cypress-bot
Copy link
Contributor

cypress-bot bot commented Mar 15, 2019

Released in 3.2.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
browser: chrome pkg/launcher This is due to an issue in the packages/launcher directory
Projects
None yet
Development

No branches or pull requests

7 participants